diff --git a/src/content/docs/alerts/organize-alerts/specify-when-alerts-create-incidents.mdx b/src/content/docs/alerts/organize-alerts/specify-when-alerts-create-incidents.mdx index aac8e2f0cdc..8903631687a 100644 --- a/src/content/docs/alerts/organize-alerts/specify-when-alerts-create-incidents.mdx +++ b/src/content/docs/alerts/organize-alerts/specify-when-alerts-create-incidents.mdx @@ -148,7 +148,7 @@ Each issue preference option has its own advantages. You can select any preferen -## One issue per policy (default) [#preference-policy] +### One issue per policy (default) [#preference-policy] Choose the **One issue per policy** preference if your policy and its conditions have a focused scope, like monitoring one entity. @@ -166,7 +166,7 @@ If additional conditions open incidents after the issue opens, the incidents are When you select the default option **One issue per policy** as your issue preference, it will group all incidents opened by any condition on that policy into the same issue. -## One issue per condition [#preference-condition] +### One issue per condition [#preference-condition] Choose the **One issue per condition** option when you want an individual issue record to focus on a specific condition. If the policy has multiple conditions, you will see separate issue records for each condition on your **Issues & activity** page. Learn more about [your issue creation preferences](/docs/new-relic-solutions/best-practices-guides/alerts-applied-intelligence/alerts-best-practices/#issue-creation). @@ -186,7 +186,7 @@ Choose the **One issue per condition** option when you want an indivi When you select the option **One issue per condition** as your issue preference, it will group all incidents by any signal for a specific condition into separate issues. -## One issue per condition and signal [#preference-signal] +### One issue per condition and signal [#preference-signal] The **One issue per condition and signal** option is the most granular level for creating issue records. Choose this issue preference when you want to closely monitor anything that is occurring anywhere across your infrastructure. Learn more about [your issue creation preferences](/docs/new-relic-solutions/best-practices-guides/alerts-applied-intelligence/alerts-best-practices/#issue-creation). diff --git a/src/content/docs/alerts/troubleshooting/missing-alert-notifications.mdx b/src/content/docs/alerts/troubleshooting/missing-alert-notifications.mdx index fed63650f81..45557b93c35 100644 --- a/src/content/docs/alerts/troubleshooting/missing-alert-notifications.mdx +++ b/src/content/docs/alerts/troubleshooting/missing-alert-notifications.mdx @@ -74,7 +74,7 @@ Here are some tips to avoid being placed on our suppression list: - In general, email isn’t the most reliable way to receive notifications. For your most important alerts, set up [alternate means of communication](/docs/alerts/new-relic-alerts/managing-notification-channels/notification-channels-control-where-send-alerts#channel-types) as a backup. + In general, email isn't the most reliable way to receive notifications. For your most important alerts, set up [alternate means of communication](/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels/) as a backup. diff --git a/src/content/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels.mdx b/src/content/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels.mdx index 6461180cce7..5a2d1163aab 100644 --- a/src/content/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels.mdx +++ b/src/content/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels.mdx @@ -7,6 +7,7 @@ tags: - Notification Channels metaDescription: 'For New Relic alerts: how you can list, create, update, and delete channels with our NerdGraph API.' redirects: + - /docs/alerts/new-relic-alerts/managing-notification-channels/notification-channels-control-where-send-alerts freshnessValidatedDate: never --- diff --git a/src/content/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/windows-linux-hybrid-cluster.mdx b/src/content/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/windows-linux-hybrid-cluster.mdx index bf52449e00c..533aee4b660 100644 --- a/src/content/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/windows-linux-hybrid-cluster.mdx +++ b/src/content/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/windows-linux-hybrid-cluster.mdx @@ -160,6 +160,6 @@ To learn more about exploring your Kubernetes data, check out these docs: diff --git a/src/content/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration.mdx b/src/content/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration.mdx index 664f57cb4d0..fd438c01eea 100644 --- a/src/content/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration.mdx +++ b/src/content/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration.mdx @@ -53,7 +53,7 @@ Take a look at what you can do with New Relic: * Scrape Prometheus metrics from any workload in the cluster thanks to the service discovery provided by the [Prometheus Agent](/docs/infrastructure/prometheus-integrations/get-started/send-prometheus-metric-data-new-relic/#Agent). -* Create [alert policies](/docs/alerts-applied-intelligence/new-relic-alerts/alert-policies/create-edit-or-find-alert-policy/) and [alert conditions](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/alert-conditions/#create-alert-condition) based on your Kubernetes data, or extend the [predefined alert conditions](/docs/integrations/kubernetes-integration/kubernetes-events/kubernetes-integration-predefined-alert-policy). +* The integration includes a set of [predefined alert conditions](/docs/kubernetes-pixie/kubernetes-integration/installation/predefined-alert-policy), but you can [create and modify your Kubernetes alerts](/docs/kubernetes-pixie/kubernetes-integration/installation/create-alerts) based on your Kubernetes data, or add a set of [recommended alert policy](/docs/kubernetes-pixie/kubernetes-integration/installation/recommended-alert-policy). * Check out all your Kubernetes events. The [Kubernetes events integration](/docs/integrations/kubernetes-integration/kubernetes-events/install-kubernetes-events-integration) watches for events happening in your Kubernetes clusters and sends those events to New Relic. You can then visualize the event data in the cluster explorer. It's installed by default after [installing the New Relic Kubernetes integration](/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-integration-install-configure/). diff --git a/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/create-alerts.mdx b/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/create-alerts.mdx new file mode 100644 index 00000000000..5becad0e831 --- /dev/null +++ b/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/create-alerts.mdx @@ -0,0 +1,140 @@ +--- +title: 'Create and modify Kubernetes alerts' +tags: + - Integrations + - Kubernetes integration + - Alerts +freshnessValidatedDate: 2024-09-02 +--- + +With New Relic, you can stay informed about Kubernetes issues by defining the specific data you want to monitor, setting customizable [thresholds](/docs/alerts/create-alert/set-thresholds/set-thresholds-alert-condition/), and configuring the [notifications](/docs/alerts/get-notified/intro-notifications/) you want to receive. You can add a set of [recommended alert policies](/docs/kubernetes-pixie/kubernetes-integration/installation/recommended-alert-policies) that you can tailor to your needs, or you can create completely custom , policies, and [workflows](/docs/alerts/get-notified/incident-workflows/) to suit your environment. + + + Check out [Alerting concepts and terms](/docs/alerts/overview/#concepts-terms) for more information about how alerts work. + + + +## Create a Kubernetes alert condition [#create-k8s-alert-condition] + +1. Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure** and click **Alerts** on the left navigation pane. + +2. Click **+ New Alert Condition**. + + Add Kubernetes alerts + +3. Choose **Kubernetes** as an alert type and define your thresholds. + + Add Kubernetes alerts + +4. Define your [thresholds](/docs/alerts/create-alert/set-thresholds/set-thresholds-alert-condition/). + +5. Configure your [alert policy](/docs/alerts/organize-alerts/create-edit-or-find-alert-policy/). You can create a new policy or add this condition to an existing policy. + +6. Set the condition status of the condition. + +7. (Optional) Add a [runbook URL](/docs/alerts/create-alert/condition-details/provide-runbook-instructions-alert-activity). + +8. Click **Create**. + + + + You can also create Kubernetes alerts using a [NRQL alert condition](/docs/alerts/create-alert/create-alert-condition/create-nrql-alert-conditions/). + + + +## Create a Kubernetes alert policy [#create-k8s-alert-condition] + +1. Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure** and click **Alerts** on the left navigation pane. + +2. Click **+ New alert policy**. + + Add Kubernetes alerts + +3. Enter a [meaningful name](/docs/alerts/organize-alerts/create-edit-or-find-alert-policy/#best-practices-policies) for the policy (maximum 64 characters). + +4. Choose the way you want to [group the incidents](/docs/alerts/organize-alerts/specify-when-alerts-create-incidents/#preference-options) from this policy. + +5. (Optional) Check the box **Suppress noise with machine learning correlation** to enable [correlation](/docs/alerts/organize-alerts/change-applied-intelligence-correlation-logic-decisions/) for the alert policy. + + Add Kubernetes alerts + +6. Click **Set up notifications**. + + +## Kubernetes alert notifications [#alert-notifications] + +Once you've configured your alert conditions, policies, and [workflows](/docs/alerts/get-notified/incident-workflows/), you'll begin to receive notifications when the threshold configured in an alert condition is triggered. You have these options: + +* [View the incident](/docs/alerts/incident-management/view-event-details-incidents/) + +* [Acknowledge the incident](/docs/alerts/get-notified/acknowledge-alert-incidents/) + +* Go to a chart of the incident data by selecting the name of the identifier. The entity identifier that triggered the alert appears near the top of the notification message. The format of the identifier depends on the alert type: + + * **Available pods are less than desired pods** alerts: + + ``` + K8s:CLUSTER_NAME:PARENT_NAMESPACE:replicaset:REPLICASET_NAME + ``` + + * **CPU or memory usage** alerts: + + ``` + K8s:CLUSTER_NAME:PARENT_NAMESPACE:POD_NAME:container:CONTAINER_NAME + ``` + + Here are some examples. + + + + For **Available pods are less than desired pods** alerts, the ID of the `ReplicaSet` triggering the issue might look like this: + + ``` + k8s:beam-production:default:replicaset:nginx-deployment-1623441481 + ``` + + This identifier contains the following information: + + * Cluster name: `beam-production` + * Parent namespace: `default` + * `ReplicaSet` name: `nginx-deployment-1623441481` + + + + For container CPU or memory usage alerts, the entity might look like this: + + ``` + k8s:beam-production:kube-system:kube-state-metrics-797bb87c75-zncwn:container:kube-state-metrics + ``` + + This identifier contains this information: + + * Cluster name: `beam-production` + * Parent namespace: `kube-system` + * Pod namespace: `kube-state-metrics-797bb87c75-zncwn` + * Container name: `kube-state-metrics` + + diff --git a/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-integration-recommended-alert-policy.mdx b/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-integration-recommended-alert-policy.mdx deleted file mode 100644 index e7d5590e9c8..00000000000 --- a/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-integration-recommended-alert-policy.mdx +++ /dev/null @@ -1,296 +0,0 @@ ---- -title: 'Kubernetes integration: Recommended alert policy' -tags: - - Integrations - - Kubernetes integration - - Installation -redirects: - - /docs/integrations/kubernetes-integration/installation/kubernetes-integration-recommended-alert-policy -freshnessValidatedDate: never ---- - -When deploying the Kubernetes integration for the first time, we deploy a default set of [alert conditions](/docs/alerts/new-relic-alerts/defining-conditions/define-alert-conditions) to your account, the [predefined alert policy](/docs/integrations/kubernetes-integration/kubernetes-events/kubernetes-integration-predefined-alert-policy), a basis for alert conditions on your Kubernetes cluster. - -While we try to tackle the most common use cases across all the environments, there's a number of additional alerts you can set up to extend the default policy. What follows are some recommendations. - -## Recommended alert conditions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Setting - - Value -
- - **Event type** - - - `K8sNodeSample` -
- - **SELECT value** - - - `(cpuUsedCores/cpuLimitCores)*100` -
- - **Warning threshold** - - - \>90% for at least 5 minutes -
- - **Critical threshold** - - - \>95% for at least 5 mins -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Setting - - Value -
- - **Event type** - - - `K8sNodeSample` -
- - **SELECT value** - - - `(memoryUsedBytes/memoryLimitBytes)/100` -
- - **Warning threshold** - - - \>85% for at least 5 minutes -
- - **Critical threshold** - - - \>95% for at least 5 mins -
- - You need to set a memory limit in your [container specs](/docs/integrations/kubernetes-integration/installation/kubernetes-integration-install-configure/#configure-integration) for [`memoryLimitBytes`](/docs/integrations/kubernetes-integration/understand-use-data/find-use-your-kubernetes-data/#container-data) to report data. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Setting - - Value -
- - **Event type** - - - `K8sPodSample` -
- - **SELECT value** - - - `isScheduled` -
- - **Warning threshold** - - -
- - **Critical threshold** - - - `isScheduled` = 0 for at least 7 minutes -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Setting - - Value -
- - **NRQL** - - - `from K8sContainerSample select latest(restartCount) - earliest(restartCount) where clusterName = '' facet containerName, podName` -
- - **Threshold** - - - `Static` -
- - **Warning threshold** - - -
- - **Critical threshold** - - - `Open incident when the query returns a value > 1 at least once in 1 minute` -
- - diff --git a/src/content/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/kubernetes-integration-predefined-alert-policy.mdx b/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/predefined-alert-policy.mdx similarity index 81% rename from src/content/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/kubernetes-integration-predefined-alert-policy.mdx rename to src/content/docs/kubernetes-pixie/kubernetes-integration/installation/predefined-alert-policy.mdx index c34faaffe0a..53a566ff04d 100644 --- a/src/content/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/kubernetes-integration-predefined-alert-policy.mdx +++ b/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/predefined-alert-policy.mdx @@ -1,5 +1,5 @@ --- -title: 'Kubernetes integration: Predefined alert policy' +title: 'Predefined alert policy' tags: - Integrations - Kubernetes integration @@ -7,14 +7,36 @@ tags: redirects: - /docs/integrations/kubernetes-integration/kubernetes-events/kubernetes-integration-predefined-alert-policy - /docs/kubernetes-pixie/kubernetes-integration/kubernetes-events/kubernetes-integration-predefined-alert-policy -freshnessValidatedDate: never + - /docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/kubernetes-integration-predefined-alert-policy/ +freshnessValidatedDate: 2024-09-02 --- -When deploying the New Relic Kubernetes integration for the first time in an account, we deploy a default set of [alert conditions](/docs/alerts/new-relic-alerts/defining-conditions/define-alert-conditions) to your account. The predefined alert policy, named **Kubernetes default alert policy**, doesn't have a [notification channel](/docs/alerts/new-relic-alerts/managing-notification-channels/notification-channels-control-where-send-alerts) by default to prevent unwanted notifications. +When deploying the New Relic Kubernetes integration for the first time in an account, we deploy a default set of predefined [alert conditions](/docs/alerts/create-alert/create-alert-condition/alert-conditions/) to your account. You don't need to do anything else. These conditions are grouped into a policy called **Kubernetes default alert policy**. This policy doesn't have a [notification channel](/docs/alerts/new-relic-alerts/managing-notification-channels/notification-channels-control-where-send-alerts) by default to prevent unwanted notifications. -You can customize the thresholds for the alert conditions, as well as update the policy to send notifications. For more information, see the [Infrastructure alerts documentation](/docs/infrastructure/new-relic-infrastructure/infrastructure-alert-conditions/infrastructure-alerts-add-edit-or-view-host-alert-information). +You can customize the [thresholds](/docs/alerts/create-alert/set-thresholds/set-thresholds-alert-condition/) for the alert conditions, as well as manage your [policies](/docs/alerts/organize-alerts/create-edit-or-find-alert-policy/) and send [notifications](/docs/alerts/get-notified/intro-notifications/). -## Predefined alert conditions + +## How to see your predefined alert policy [#see-predefined-alert-policy] + +To view the default predefined alert policy set after deploying the integration, do this: + +1. Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts**. + +2. Click **Alert Policies** in the left navigation pane. + +3. Click **Kubernetes default alert policy**. + + + Add Kubernetes alerts + + +## Predefined Kubernetes alert conditions [#predefined-alert-conditions] + +This is the default set of alert conditions installed when you deploy the New Relic Kubernetes integration: ReplicaSet doesn't have desired amount of pods} > @@ -434,7 +456,7 @@ You can customize the thresholds for the alert conditions, as well as update the etcd open file descriptors} >
@@ -502,6 +524,3 @@ You can customize the thresholds for the alert conditions, as well as update the -## Create new alert conditions [#create-policies] - -To create new alert conditions based on Kubernetes metric data, see [Manage alerts](/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/find-use-your-kubernetes-data/#alerts). diff --git a/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/recommended-alert-policy.mdx b/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/recommended-alert-policy.mdx new file mode 100644 index 00000000000..954e470e34e --- /dev/null +++ b/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/recommended-alert-policy.mdx @@ -0,0 +1,453 @@ +--- +title: 'Recommended alert policy' +tags: + - Integrations + - Kubernetes integration + - Alert policies +redirects: + - /docs/integrations/kubernetes-integration/installation/kubernetes-integration-recommended-alert-policy + - /docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-integration-recommended-alert-policy/ +freshnessValidatedDate: 2024-09-02 +--- + + +When you first [install the Kubernetes integration](/install/kubernetes/), we deploy a default set of recommended alerts conditions to your account that form the basis for alert conditions on your Kubernetes cluster. These conditions are grouped into a policy called **Kubernetes alert policy**. + +While we've tried to address the most common use cases in all environments, there are a number of additional alerts you can set up to extend the default policy. These are our recommended alerting policies. + +## Adding the recommended alert policy [#add-recommended-alert-policy] + +To add recommended alert policy, follow these steps: + +1. Go to **[one.newrelic.com](https://one.newrelic.com) > + Integrations & Agents**. + +2. Select **Alerts** to access the pre-built resources. + + Add Kubernetes alerts + +3. Search **Kubernetes** and select the recommended alert policy you want to add. + + Add Kubernetes alerts + + +## How to see the recommended alert policy [#see-recommended-alert-policy] + +To view the recommended alert policy you've added, do this: + +1. Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts**. + +2. Click **Alert Policies** in the left navigation pane. + +3. You'll see **Kubernetes alert policy** and **Google Kubernetes engine alert policy**. + + + Add Kubernetes alerts + + +## Kubernetes alert policy [#k8s-alert-conditions] + +This is the default set of recommended alert conditions you'll add: + + + + This alert condition generates an alert when a container is throttled by more than 25% for more than 5 minutes. It runs this query: + + ```sql + FROM K8sContainerSample + SELECT sum(containerCpuCfsThrottledPeriodsDelta) / sum(containerCpuCfsPeriodsDelta) * 100 + WHERE clusterName in ('YOUR_CLUSTER_NAME') and namespaceName in ('YOUR_NAMESPACE_NAME') facet containerName, podName, namespaceName, clusterName + ``` + + See the [GitHub configuration file](https://github.com/newrelic/newrelic-quickstarts/blob/main/alert-policies/kubernetes/ContainerCPUThrottling.yaml) for more info. + + + + + This alert condition generates an alert when the average container CPU usage against the limit exceeds 90% for over 5 minutes. It runs this query: + + ```sql + FROM K8sContainerSample + SELECT average(cpuCoresUtilization) + WHERE clusterName in ('YOUR_CLUSTER_NAME') and namespaceName in ('YOUR_NAMESPACE_NAME') facet containerName, podName, namespaceName, clusterName + ``` + + See the [GitHub configuration file](https://github.com/newrelic/newrelic-quickstarts/blob/main/alert-policies/kubernetes/ContainerHighCPUUtil.yaml) for more info. + + + + + This alert condition generates an alert when the average container memory usage against the limit exceeds 90% for over 5 minutes. It runs this query: + + ```sql + FROM K8sContainerSample + SELECT average(memoryWorkingSetUtilization) + WHERE clusterName in ('YOUR_CLUSTER_NAME') and namespaceName in ('YOUR_NAMESPACE_NAME') facet containerName, podName, namespaceName, clusterName + ``` + + See the [GitHub configuration file](https://github.com/newrelic/newrelic-quickstarts/blob/main/alert-policies/kubernetes/ContainerHighMemUtil.yaml) for more info. + + + + This alert condition generates an alert when container restarts exceed 0 in a 5-minute sliding window. It runs this query: + + ```sql + FROM K8sContainerSample + SELECT sum(restartCountDelta) + WHERE clusterName in ('YOUR_CLUSTER_NAME') and namespaceName in ('YOUR_NAMESPACE_NAME') facet containerName, podName, namespaceName, clusterName + ``` + + See the [GitHub configuration file](https://github.com/newrelic/newrelic-quickstarts/blob/main/alert-policies/kubernetes/ContainerRestarting.yaml) for more info. + + + + This alert condition generates an alert when a container waits over 5 minutes. It runs this query: + + ```sql + FROM K8sContainerSample + SELECT uniqueCount(podName) + WHERE status = 'Waiting' and clusterName in ('YOUR_CLUSTER_NAME') and namespaceName in ('YOUR_NAMESPACE_NAME') FACET containerName, podName, namespaceName, clusterName + ``` + + See the [GitHub configuration file](https://github.com/newrelic/newrelic-quickstarts/blob/main/alert-policies/kubernetes/ContainerWaiting.yaml) for more info. + + + + This alert condition generates an alert when the daemonset is missing any pods for a period longer than 5 minutes. It runs this query: + + ```sql + FROM K8sDaemonsetSample + SELECT latest(podsMissing) + WHERE clusterName in ('YOUR_CLUSTER_NAME') and namespaceName in ('YOUR_NAMESPACE_NAME') facet daemonsetName, namespaceName, clusterName + ``` + + See the [GitHub configuration file](https://github.com/newrelic/newrelic-quickstarts/blob/main/alert-policies/kubernetes/DaemonsetPodsMissing.yaml) for more info. + + + + + This alert condition generates an alert when the deployment is missing any pods for a period longer than 5 minutes. It runs this query: + + ```sql + FROM K8sDeploymentSample + SELECT latest(podsMissing) + WHERE clusterName in ('YOUR_CLUSTER_NAME') and namespaceName in ('YOUR_NAMESPACE_NAME') facet deploymentName, namespaceName, clusterName + ``` + + See the [GitHub configuration file](https://github.com/newrelic/newrelic-quickstarts/blob/main/alert-policies/kubernetes/DeploymentPodsMissing.yaml) for more info. + + + + Etcd file descriptor utilization is high} + > + This alert condition generates an alert when the `Etcd` file descriptor usage exceeds 90% for over 5 minutes. It runs this query: + + ```sql + FROM K8sEtcdSample + SELECT max(processFdsUtilization) + WHERE clusterName in ('YOUR_CLUSTER_NAME') facet displayName, clusterName + ``` + + See the [GitHub configuration file](https://github.com/newrelic/newrelic-quickstarts/blob/main/alert-policies/kubernetes/EtcdFileDescriptors.yaml) for more info. + + + Etcd has no leader} + > + This alert condition generates an alert when the `Etcd` file descriptor is leaderless for over 1 minute. It runs this query: + + ```sql + FROM K8sEtcdSample + SELECT min(etcdServerHasLeader) + WHERE clusterName in ('YOUR_CLUSTER_NAME') facet displayName, clusterName + ``` + + See the [GitHub configuration file](https://github.com/newrelic/newrelic-quickstarts/blob/main/alert-policies/kubernetes/EtcdHasNoLeader.yaml) for more info. + + + + This alert condition generates an alert when the current replicas of a horizontal pod autoscaler are lower than the desired replicas for more than 5 minutes. It runs this query: + + ```sql + FROM K8sHpaSample + SELECT latest(desiredReplicas - currentReplicas) + WHERE clusterName in ('YOUR_CLUSTER_NAME') and namespaceName in ('YOUR_NAMESPACE_NAME') facet displayName, namespaceName, clusterName + ``` + + See the [GitHub configuration file](https://github.com/newrelic/newrelic-quickstarts/blob/main/alert-policies/kubernetes/HPAMissingReplicas.yaml) for more info. + + + + This alert condition generates an alert when a horizontal pod autoscaler exceeds 5 replicas. It runs this query: + + ```sql + FROM K8sHpaSample + SELECT latest(maxReplicas - currentReplicas) + WHERE clusterName in ('YOUR_CLUSTER_NAME') and namespaceName in ('YOUR_NAMESPACE_NAME') facet displayName, namespaceName, clusterName + ``` + + See the [GitHub configuration file](https://github.com/newrelic/newrelic-quickstarts/blob/main/alert-policies/kubernetes/HPAMaxReplicas.yaml) for more info. + + + + This alert condition generates an alert when a job reports a failed status. It runs this query: + + ```sql + FROM K8sJobSample + SELECT uniqueCount(jobName) + WHERE failed = 'true' and clusterName in ('YOUR_CLUSTER_NAME') and namespaceName in ('YOUR_NAMESPACE_NAME') facet jobName, namespaceName, clusterName, failedPodsReason + ``` + + See the [GitHub configuration file](https://github.com/newrelic/newrelic-quickstarts/blob/main/alert-policies/kubernetes/JobFailed.yaml) for more info. + + + + This alert condition generates an alert when more than 5 pods in a namespace fail for more than 5 minutes. It runs this query: + + ```sql + FROM K8sPodSample + SELECT uniqueCount(podName) + WHERE clusterName in ('YOUR_CLUSTER_NAME') and namespaceName in ('YOUR_NAMESPACE_NAME') and status = 'Failed' facet namespaceName, clusterName + ``` + + See the [GitHub configuration file](https://github.com/newrelic/newrelic-quickstarts/blob/main/alert-policies/kubernetes/PodsFailingNamespace.yaml) for more info. + + + + This alert condition generates an alert when the average node allocable CPU utilization exceeds 90% for more than 5 minutes. It runs this query: + + ```sql + FROM K8sNodeSample + SELECT average(allocatableCpuCoresUtilization) + WHERE clusterName in ('YOUR_CLUSTER_NAME') facet nodeName, clusterName + ``` + + See the [GitHub configuration file](https://github.com/newrelic/newrelic-quickstarts/blob/main/alert-policies/kubernetes/NodeHighAllocatableCPUUtil.yaml) for more info. + + + + This alert condition generates an alert when the average node allocable memory utilization exceeds 90% for more than 5 minutes. It runs this query: + + ```sql + FROM K8sNodeSample + SELECT average(allocatableMemoryUtilization) + WHERE clusterName in ('YOUR_CLUSTER_NAME') facet nodeName, clusterName + ``` + + See the [GitHub configuration file](https://github.com/newrelic/newrelic-quickstarts/blob/main/alert-policies/kubernetes/NodeHighAllocatableMemUtil.yaml) for more info. + + + + This alert condition generates an alert when a node is unavailable for 5 minutes. It runs this query: + + ```sql + FROM K8sNodeSample + SELECT latest(condition.Ready) + WHERE clusterName in ('YOUR_CLUSTER_NAME') facet nodeName, clusterName + ``` + + See the [GitHub configuration file](https://github.com/newrelic/newrelic-quickstarts/blob/main/alert-policies/kubernetes/NodeIsNotReady.yaml) for more info. + + + + This alert condition generates an alert when a node is marked unscheduled. It runs this query: + + ```sql + FROM K8sNodeSample + SELECT latest(unschedulable) + WHERE clusterName in ('YOUR_CLUSTER_NAME') facet nodeName, clusterName + ``` + + See the [GitHub configuration file](https://github.com/newrelic/newrelic-quickstarts/blob/main/alert-policies/kubernetes/NodeUnschedulable.yaml) for more info. + + + + This alert condition generates an alert when a node's running pods exceed 90% of the node's pod capacity for more than 5 minutes. It runs this query: + + ```sql + FROM K8sPodSample, K8sNodeSample + SELECT ceil(filter(uniqueCount(podName) + WHERE status = 'Running') / latest(capacityPods) * 100) as 'Pod Capacity %' where nodeName != '' and nodeName is not null and clusterName in ('YOUR_CLUSTER_NAME') facet nodeName, clusterName + ``` + + See the [GitHub configuration file](https://github.com/newrelic/newrelic-quickstarts/blob/main/alert-policies/kubernetes/NodePodCapacity.yaml) for more info. + + + + This alert condition generates an alert when the average node root file system capacity utilization exceeds 90% for more than 5 minutes. It runs this query: + + ```sql + FROM K8sNodeSample + SELECT average(fsCapacityUtilization) + WHERE clusterName in ('YOUR_CLUSTER_NAME') facet nodeName, clusterName + ``` + + See the [GitHub configuration file](https://github.com/newrelic/newrelic-quickstarts/blob/main/alert-policies/kubernetes/NodeHighFSCapacityUtil.yaml) for more info. + + + + This alert condition generates an alert when persistent volume is in a failed or pending state for more than 5 minutes. It runs this query: + + ```sql + FROM K8sPersistentVolumeSample + SELECT uniqueCount(volumeName) + WHERE statusPhase in ('Failed','Pending') and clusterName in ('YOUR_CLUSTER_NAME') facet volumeName, clusterName + ``` + + See the [GitHub configuration file](https://github.com/newrelic/newrelic-quickstarts/blob/main/alert-policies/kubernetes/PersistentVolumeErrors.yaml) for more info. + + + + This alert condition generates an alert when a pod is unable to be scheduled for more than 5 minutes. It runs this query: + + ```sql + FROM K8sPodSample + SELECT latest(isScheduled) + WHERE clusterName in ('YOUR_CLUSTER_NAME') and namespaceName in ('YOUR_NAMESPACE_NAME') facet podName, namespaceName, clusterName + ``` + + See the [GitHub configuration file](https://github.com/newrelic/newrelic-quickstarts/blob/main/alert-policies/kubernetes/PodNotScheduled.yaml) for more info. + + + + This alert condition generates an alert when a pod is unavailable for over 5 minutes. It runs this query: + + ```sql + FROM K8sPodSample + SELECT latest(isReady) + WHERE status not in ('Failed', 'Succeeded') where clusterName in ('YOUR_CLUSTER_NAME') and namespaceName in ('YOUR_NAMESPACE_NAME') facet podName, namespaceName, clusterName + ``` + + See the [GitHub configuration file](https://github.com/newrelic/newrelic-quickstarts/blob/main/alert-policies/kubernetes/PodNotReady.yaml) for more info. + + + statefulset is missing pods} + > + This alert condition generates an alert when `statefulset` is missing pods over 5 minutes. It runs this query: + + ```sql + FROM K8sStatefulsetSample + SELECT latest(podsMissing) + WHERE clusterName in ('YOUR_CLUSTER_NAME') and namespaceName in ('YOUR_NAMESPACE_NAME') facet daemonsetName, namespaceName, clusterName + ``` + + See the [GitHub configuration file](https://github.com/newrelic/newrelic-quickstarts/blob/main/alert-policies/kubernetes/StatefulsetPodsMissing.yaml) for more info. + + + + + +## Google Kubernetes engine alert policy [#google-alert-policies] + +This is the default set of recommended Google Kubernetes engine alert conditions you'll add: + + + + This alert condition generates an alert when a node's CPU utilization exceeds 90% for at least 15 minutes. It runs this query: + + ```sql + FROM Metric + SELECT max(`gcp.kubernetes.node.cpu.allocatable_utilization`) * 100 + WHERE clusterName LIKE '%' FACET gcp.kubernetes.nodeName + ``` + + See the [GitHub configuration file](https://github.com/newrelic/newrelic-quickstarts/blob/main/alert-policies/google-kubernetes-engine/HighCPU.yml) for more info. + + + This alert condition generates an alert when a node's memory usage exceeds 85% of its total capacity. It runs this query: + + ```sql + FROM K8sPodSample + SELECT max(gcp.kubernetes.node.memory.allocatable_utilization) * 100 + WHERE clusterName LIKE '%' FACET gcp.kubernetes.nodeName + ``` + + See the [GitHub configuration file](https://github.com/newrelic/newrelic-quickstarts/blob/main/alert-policies/google-kubernetes-engine/HighMemoryUsage.yml) for more info. + + + + + + diff --git a/src/content/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/find-use-your-kubernetes-data.mdx b/src/content/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/find-use-your-kubernetes-data.mdx index b442c3e92fc..1b65cdcb4c9 100644 --- a/src/content/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/find-use-your-kubernetes-data.mdx +++ b/src/content/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/find-use-your-kubernetes-data.mdx @@ -341,7 +341,7 @@ Kubernetes data is attached to these [events](/docs/using-new-relic/data/underst View your Kubernetes events -Check our Kubernetes default alert policy +Check our Kubernetes recommended alert policies diff --git a/src/content/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer.mdx b/src/content/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer.mdx index 4b5583b6879..aa3c4611176 100644 --- a/src/content/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer.mdx +++ b/src/content/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer.mdx @@ -300,7 +300,7 @@ The cluster explorer represents your most relevant cluster data on a chart with src="/images/kubernetes_screenshot-crop_cluster-explorer-rings.webp" /> -Hover the mouse over each node or pod to get a quick overview of its resource usage. You can click each node and pod to view its resource usage over time or to get more information about its health and active alerts. [Colors](/docs/alerts/new-relic-alerts/configuring-alert-policies/identify-entities-without-alert-policies) are based on [predefined alert conditions](/docs/integrations/kubernetes-integration/kubernetes-events/kubernetes-integration-predefined-alert-policy): Yellow pods have active warning alerts, while red pods have active critical alerts. +Hover the mouse over each node or pod to get a quick overview of its resource usage. You can click each node and pod to view its resource usage over time or to get more information about its health and active alerts. [Colors](/docs/alerts/new-relic-alerts/configuring-alert-policies/identify-entities-without-alert-policies) are based on [recommended alert policies](/docs/kubernetes-pixie/kubernetes-integration/installation/recommended-alert-policies): Yellow pods have active warning alerts, while red pods have active critical alerts. - In the context of alerts, an alert policy is a collection of one or more [alert conditions](/docs/alerts/new-relic-alerts/defining-conditions/define-alert-conditions), one or more [notification channels](/docs/alerts/new-relic-alerts/managing-notification-channels/notification-channels-control-where-send-alerts), and an [**Incident preference**](/docs/alerts/new-relic-alerts/configuring-alert-policies/specify-when-new-relic-creates-incidents) setting. + In the context of alerts, an alert policy is a collection of one or more [alert conditions](/docs/alerts/new-relic-alerts/defining-conditions/define-alert-conditions), one or more [notification channels](/docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels/), and an [**Incident preference**](/docs/alerts/new-relic-alerts/configuring-alert-policies/specify-when-new-relic-creates-incidents) setting. A condition contained within a policy may open an incident depending on the [incident preference settings](/docs/alerts-applied-intelligence/new-relic-alerts/alert-policies/specify-when-alerts-create-incidents). In this case, all channels attached to the policy will generate notifications. diff --git a/src/content/docs/security/security-privacy/data-privacy/data-privacy-new-relic.mdx b/src/content/docs/security/security-privacy/data-privacy/data-privacy-new-relic.mdx index 9a699bdda7a..552b1123aee 100644 --- a/src/content/docs/security/security-privacy/data-privacy/data-privacy-new-relic.mdx +++ b/src/content/docs/security/security-privacy/data-privacy/data-privacy-new-relic.mdx @@ -121,7 +121,7 @@ Our role-based account structure gives you direct control over who can access or By default, we communicate with you for a variety of purposes related to your status as New Relic subscribers. This includes product engagement, support, alert notifications, updates, billings, etc. * Individual users can unsubscribe from certain communications. General email preferences are managed through the account user interface. For more information, see [Account email settings](/docs/accounts/accounts/account-maintenance/account-email-settings). - * [Alert notification emails](/docs/alerts/new-relic-alerts/managing-notification-channels/notification-channels-control-where-send-alerts#email) are managed through the alerting UI. + * [Alert notification emails](//docs/apis/nerdgraph/examples/nerdgraph-api-notifications-channels/) are managed through the alerting UI. * New Relic customers should be vigilant of phishing attempts that target their employees. New Relic also makes available SAML, SSO, and SCIM provisioning, which is available here. Additionally, customers configured with SAML, SSO, and SCIM, are strongly encouraged to enable MFA. diff --git a/src/content/whats-new/2021/03/kubernetes-whats-new.md b/src/content/whats-new/2021/03/kubernetes-whats-new.md index e655a221a50..bacaa244f45 100644 --- a/src/content/whats-new/2021/03/kubernetes-whats-new.md +++ b/src/content/whats-new/2021/03/kubernetes-whats-new.md @@ -10,7 +10,7 @@ The `container_memory_usage_bytes` metric isn't an accurate indicator for out of This change will be reflected within New Relic One as follows: ​ ​ -* [Kubernetes integration: Predefined alert policy.](https://docs.newrelic.com/docs/integrations/kubernetes-integration/kubernetes-events/kubernetes-integration-predefined-alert-policy/) The “Container memory usage % is too high” alert condition now uses the new `memoryWorkingSetUtilization` attribute instead of (`memoryUsedBytes`/`memoryLimitBytes`)/100. +* [Predefined alert conditions.](https://docs.newrelic.com/docs/kubernetes-pixie/kubernetes-integration/installation/predefined-alert-conditions) The “Container memory usage % is too high” alert condition now uses the new `memoryWorkingSetUtilization` attribute instead of (`memoryUsedBytes`/`memoryLimitBytes`)/100. * **Please note that existing alert conditions won’t be automatically updated. If you are using our predefined alert policy, we strongly recommend you to update it accordingly.** * The following widgets are now using working set bytes in Kubernetes dashboard: * Resources Used diff --git a/src/content/whats-new/2024/09/.gitkeep b/src/content/whats-new/2024/09/.gitkeep deleted file mode 100644 index e69de29bb2d..00000000000 diff --git a/src/content/whats-new/2024/09/whats-new-09-03-loss-of-signal-standalone.md b/src/content/whats-new/2024/09/whats-new-09-03-loss-of-signal-standalone.md new file mode 100644 index 00000000000..d656453f4e8 --- /dev/null +++ b/src/content/whats-new/2024/09/whats-new-09-03-loss-of-signal-standalone.md @@ -0,0 +1,25 @@ +--- +title: "New alert condition threshold type: stand-alone loss of signal" +summary: 'Get alerted when New Relic stops receiving data!' +releaseDate: '2024-09-03' +learnMoreLink: 'https://docs.newrelic.com/docs/alerts/create-alert/create-alert-condition/create-nrql-alert-conditions/#signal-loss' +--- + + +The loss of signal threshold capabilities have been extended and are now available as the sole threshold option for an alert configuration with any entity type. Previously, you could only configure a loss of signal threshold as an additional threshold value to any static or anomaly condition. What if you want an alert condition that is only monitoring the presence of a signal or data flowing though? + +## Create a stand-alone threshold +Now, you can create an alert condition with a stand-alone loss of signal threshold and specify how long the signal must be lost before opening a violation. The additional anomaly or static threshold(s) are optional. + +The stand-alone loss of signal evaluation is similar to the way it works today in conjunction with static or anomaly conditions: There must be a signal that is detected first in order for the signal to meet the threshold of being “lost.” Entity status will function as it does today when a loss of signal occurs: An impacted entity will move into “critical” status when the signal is lost for the amount of time specified. + +Here's what a stand-alone threshold for loss of signal looks like in the condition builder: + +![Condition builder UI showing only Loss of Signal threhold configured](/images/whats-new-signal-loss-standalone.webp "Condition builder UI showing only Loss of Signal threhold configured") + +## Manage expected terminations +We have also added a new feature to the loss of signal threshold that allows you to specify when a termination is expected. You can do this for entities with the `termination: expected` tag (formerly called `clean shut down` on host entities). This allows you to use a broad condition to evaluate many entities and avoid alerts from entities that do not have consistent signal-stop reporting. + + + + diff --git a/src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/windows-linux-hybrid-cluster.mdx b/src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/windows-linux-hybrid-cluster.mdx index 76382da3f4b..f731eb5cfc8 100644 --- a/src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/windows-linux-hybrid-cluster.mdx +++ b/src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/windows-linux-hybrid-cluster.mdx @@ -162,6 +162,6 @@ Para obtener más información sobre cómo explorar sus datos de Kubernetes, con diff --git a/src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration.mdx b/src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration.mdx index 53d6938a200..a8b03dff2a7 100644 --- a/src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration.mdx +++ b/src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration.mdx @@ -37,7 +37,7 @@ Echa un vistazo a lo que puedes hacer con New Relic: * Elimina Prometheus métrica de cualquier carga de trabajo en el clúster gracias al servicio de descubrimiento proporcionado por el [agente Prometheus](/docs/infrastructure/prometheus-integrations/get-started/send-prometheus-metric-data-new-relic/#Agent). -* Cree [una política de alertas](/docs/alerts-applied-intelligence/new-relic-alerts/alert-policies/create-edit-or-find-alert-policy/) y [una condición de alerta](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/alert-conditions/#create-alert-condition) basadas en sus datos Kubernetes , o extienda la [condición de alerta predefinida](/docs/integrations/kubernetes-integration/kubernetes-events/kubernetes-integration-predefined-alert-policy). +* Cree [una política de alertas](/docs/alerts-applied-intelligence/new-relic-alerts/alert-policies/create-edit-or-find-alert-policy/) y [una condición de alerta](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/alert-conditions/#create-alert-condition) basadas en sus datos Kubernetes, o extienda la [condición de alerta predefinida](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-prebuilt-alert-policies). * Consulta todos tus eventos Kubernetes . La [integración de eventosKubernetes ](/docs/integrations/kubernetes-integration/kubernetes-events/install-kubernetes-events-integration)vigila los eventos que suceden en su clúster de Kubernetes y los envía a New Relic. Luego puede visualizar los datos del evento en el explorador de clústeres. Se instala de forma predeterminada luego de [instalar la integración de New Relic Kubernetes](/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-integration-install-configure/). diff --git a/src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/kubernetes-integration-predefined-alert-policy.mdx b/src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-prebuilt-alert-policies.mdx similarity index 100% rename from src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/kubernetes-integration-predefined-alert-policy.mdx rename to src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-prebuilt-alert-policies.mdx diff --git a/src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-integration-recommended-alert-policy.mdx b/src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-recommended-alert-policies.mdx similarity index 97% rename from src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-integration-recommended-alert-policy.mdx rename to src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-recommended-alert-policies.mdx index 396e009b2bf..aaf15a9bbf8 100644 --- a/src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-integration-recommended-alert-policy.mdx +++ b/src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-recommended-alert-policies.mdx @@ -8,7 +8,7 @@ freshnessValidatedDate: never translationType: machine --- -Cuando implementamos la integración Kubernetes por primera vez, implementamos un conjunto predeterminado de [condición de alerta](/docs/alerts/new-relic-alerts/defining-conditions/define-alert-conditions) en su cuenta, la [política de alertas predefinida](/docs/integrations/kubernetes-integration/kubernetes-events/kubernetes-integration-predefined-alert-policy), una base para la condición de alerta en su clúster de Kubernetes. +Cuando implementamos la integración Kubernetes por primera vez, implementamos un conjunto predeterminado de [condición de alerta](/docs/alerts/new-relic-alerts/defining-conditions/define-alert-conditions) en su cuenta, la [política de alertas predefinida](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-prebuilt-alert-policies), una base para la condición de alerta en su clúster de Kubernetes. Si bien intentamos abordar los casos de uso más comunes en todos los entornos, hay una serie de alertas adicionales que puede configurar para ampliar la política predeterminada. Lo que sigue son algunas recomendaciones. diff --git a/src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/find-use-your-kubernetes-data.mdx b/src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/find-use-your-kubernetes-data.mdx index ac55eb6ef21..28b778a4aa0 100644 --- a/src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/find-use-your-kubernetes-data.mdx +++ b/src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/find-use-your-kubernetes-data.mdx @@ -9,25 +9,25 @@ freshnessValidatedDate: never translationType: machine --- -Puedes crear tus propios [gráficos](/docs/query-your-data/explore-query-data/use-charts/use-your-charts/) y [consultar](/docs/query-your-data/explore-query-data/get-started/introduction-querying-new-relic-data/) todos tus datos [de integración Kubernetes ](/docs/integrations/kubernetes-integration/get-started/introduction-kubernetes-integration)empleando el generador de consultas y la API NerdGraph. Nuestra integración recopila datos Kubernetes instrumentando la capa de orquestación del contenedor. +Puedes crear tus propios gráficos y [consultar](/docs/using-new-relic/data/understand-data/query-new-relic-data) todos tus datos [de integración Kubernetes ](/docs/integrations/kubernetes-integration/get-started/introduction-kubernetes-integration)utilizando el generador de consultas y la API NerdGraph. Nuestra integración recopila datos Kubernetes instrumentando la capa de orquestación del contenedor. Para una experiencia más sencilla y visual, utiliza el [explorador de clústeres](/docs/integrations/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer). -New Relic - Kubernetes dashboard +New Relic - Kubernetes dashboard
- Ir a **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Dashboards**. Usando el [generador de consultas](/docs/chart-builder/use-chart-builder/get-started/introduction-chart-builder) puedes consultar tus datos Kubernetes y crear visualizaciones claras. + **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Dashboards**: Utilizando el [generador de consultas](/docs/chart-builder/use-chart-builder/get-started/introduction-chart-builder) puedes consultar tus datos Kubernetes y crear visualizaciones claras.
- - Si prefiere una experiencia visual de sus datos Kubernetes , consulte nuestro [explorador de clúster de Kubernetes ](/docs/integrations/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer). - - ## Consultar datos Kubernetes [#view-data] La forma más sencilla de [consultar tus datos Kubernetes ](/docs/using-new-relic/data/understand-data/query-new-relic-data)es utilizando el [generador de consultas](/docs/query-your-data/explore-query-data/query-builder/use-advanced-nrql-mode-specify-data), que acepta [consultasNRQL ](/docs/query-data/nrql-new-relic-query-language/getting-started/introduction-nrql). Alternativamente, puede utilizar la [API NerdGraph](/docs/apis/nerdgraph/get-started/introduction-new-relic-nerdgraph) para recuperar datos de Kubernetes. ### Evento y atributo [#event-types] -Los datos Kubernetes se anexan a estos [eventos](/docs/using-new-relic/data/understand-data/new-relic-data-types#event-data). Aquí hay una lista de eventos específicos para Kubernetes (obtenga más información sobre estos datos en [nuestro diccionario de datos](/attribute-dictionary/?dataSource=Kubernetes)). +Los datos Kubernetes se adjuntan al siguiente [evento](/docs/using-new-relic/data/understand-data/new-relic-data-types#event-data). Puede obtener más información sobre estos datos en [nuestro diccionario de datos](/attribute-dictionary/?dataSource=Kubernetes).
@@ -315,9 +315,11 @@ Los datos Kubernetes se anexan a estos [eventos](/docs/using-new-relic/data/unde
+Para obtener más información sobre estos eventos y sus atributos, consulte [nuestro diccionario de datos](/attribute-dictionary/?dataSource=Kubernetes). + ### Metadatos Kubernetes en APM-aplicación de monitorización [#apm-custom-attributes] -[Conectar su aplicación a Kubernetes](/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/link-apm-applications-kubernetes/) agrega estos atributos a los datos de su aplicación, así como a los metadatos del rastreo distribuido: +[Al vincular su aplicación con Kubernetes](/docs/integrations/kubernetes-integration/metadata-injection/kubernetes-apm-metadata-injection), se agregan los siguientes atributos a la aplicación traza y rastreo distribuido: * `nodeName` * `containerName` @@ -326,10 +328,125 @@ Los datos Kubernetes se anexan a estos [eventos](/docs/using-new-relic/data/unde * `deploymentName` * `namespaceName` -## Elige tu próximo paso [#next-step] +## Administrar alertas [#alerts] + +Puedes recibir notificaciones sobre e incidentes relacionados con tus datos Kubernetes : + + + + Para crear una condición de alerta para la integración de Kubernetes: + + 1. Vaya a **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure > Settings > Alerts > Kubernetes** y luego seleccione **Create alert condition**. + + 2. Para filtrar la alerta a la entidad Kubernetes que solo tiene el atributo elegido, seleccione **Filter**. + + 3. Seleccione la configuración del umbral. Para obtener más información sobre las opciones **Trigger an alert when...** , consulte [Tipos de alerta](#alert-types). + + 4. Seleccione una [política de alertas](/docs/alerts/new-relic-alerts/configuring-alert-policies/create-or-rename-alert-policy) existente o cree una nueva. + + 5. Seleccione **Create**. + + Cuando se activa el umbral de una condición de alerta, New Relic envía una [notificación](#notifications) al canal de notificación de la póliza. + + + + La integración Kubernetes viene con su propia política de alertas y condición de alerta. Para ver cuáles son las condiciones de alerta predefinidas, consulte [Integración Kubernetes: Política de alertas predefinida](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-prebuilt-alert-policies). + + Además, puede crear una condición de alerta para cualquier métrica recopilada por cualquier [integración de New Relic](/docs/integrations/new-relic-integrations/getting-started/introduction-infrastructure-integrations) que utilice, incluida la integración de Kubernetes: + + 1. Seleccione el tipo de alerta + + + **Integrations** + + + . + + 2. En el menú desplegable + + + **Select a data source** + + + , seleccione una fuente de datos de Kubernetes (K8). + + + + Cuando se activa el umbral de una condición de alerta, New Relic envía un mensaje al canal de notificación elegido en la política de alertas. Dependiendo del tipo de notificación, podrá tener las siguientes opciones: + + * [Ver el incidente](/docs/alerts-applied-intelligence/new-relic-alerts/alert-incidents/view-event-details-incidents). + + * [Reconocer el incidente](/docs/alerts/new-relic-alerts/reviewing-alert-incidents/acknowledge-alert-incidents). + + * Vaya a un gráfico de datos del incidente seleccionando el nombre del identificador. + + El identificador de entidad que activó la alerta aparece cerca de la parte superior del mensaje de notificación. El formato del identificador depende del tipo de alerta: + + * **Available pods are less than desired pods** alertas: + + ``` + K8s:CLUSTER_NAME:PARENT_NAMESPACE:replicaset:REPLICASET_NAME + ``` + + * **CPU or memory usage** alertas: + + ``` + K8s:CLUSTER_NAME:PARENT_NAMESPACE:POD_NAME:container:CONTAINER_NAME + ``` + + Aquí hay unos ejemplos. + + + + Para las alertas **Available pods are less than desired pods**, el ID del `ReplicaSet` que desencadena el problema podría tener este aspecto: + + ``` + k8s:beam-production:default:replicaset:nginx-deployment-1623441481 + ``` + + Este identificador contiene la siguiente información: + + * Nombre del clúster: `beam-production` + * Namespace principal: `default` + * `ReplicaSet` nombre: `nginx-deployment-1623441481` + + + + Para alertas de uso de memoria o CPU del contenedor, la entidad podría verse así: + + ``` + k8s:beam-production:kube-system:kube-state-metrics-797bb87c75-zncwn:container:kube-state-metrics + ``` + + Este identificador contiene la siguiente información: - - Ver tu evento Kubernetes + * Nombre del clúster: `beam-production` + * Namespace principal: `kube-system` + * Pod namespace: `kube-state-metrics-797bb87c75-zncwn` + * Nombre del contenedor: `kube-state-metrics` + + + - Consulta nuestra política de alertas predeterminada de Kubernetes - \ No newline at end of file + + Siga los procedimientos estándar para [crear una condición de alerta para la consulta NRQL](/docs/alerts/new-relic-alerts/defining-conditions/create-alert-conditions-nrql-queries). + + diff --git a/src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer.mdx b/src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer.mdx index f31e75b70e9..de23bf4a7d8 100644 --- a/src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer.mdx +++ b/src/i18n/content/es/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer.mdx @@ -253,7 +253,7 @@ El explorador de clústeres representa los datos del clúster más relevantes en New Relic - Cluster explorer -Pase el mouse sobre cada nodo o pod para obtener una descripción general rápida de su uso de recursos. Puede hacer clic en cada nodo y pod para ver su uso de recursos a lo largo del tiempo u obtener más información sobre su estado y alertas activas. [Los colores](/docs/alerts/new-relic-alerts/configuring-alert-policies/identify-entities-without-alert-policies) se basan en [una condición de alerta predefinida](/docs/integrations/kubernetes-integration/kubernetes-events/kubernetes-integration-predefined-alert-policy): el grupo amarillo tiene alertas de advertencia activas, mientras que el grupo rojo tiene alerta crítica activa. +Pase el mouse sobre cada nodo o pod para obtener una descripción general rápida de su uso de recursos. Puede hacer clic en cada nodo y pod para ver su uso de recursos a lo largo del tiempo u obtener más información sobre su estado y alertas activas. [Los colores](/docs/alerts/new-relic-alerts/configuring-alert-policies/identify-entities-without-alert-policies) se basan en [una condición de alerta predefinida](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-prebuilt-alert-policies): el grupo amarillo tiene alertas de advertencia activas, mientras que el grupo rojo tiene alerta crítica activa. New Relic - Cluster explorer - Pod alert diff --git a/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/windows-linux-hybrid-cluster.mdx b/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/windows-linux-hybrid-cluster.mdx index dad48ef33d0..c53a63e29c8 100644 --- a/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/windows-linux-hybrid-cluster.mdx +++ b/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/windows-linux-hybrid-cluster.mdx @@ -161,7 +161,7 @@ Kubernetes データの探索について詳しくは、次のドキュメント /> diff --git a/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration.mdx b/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration.mdx index 6b24730193b..92dc31e2cd3 100644 --- a/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration.mdx +++ b/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration.mdx @@ -37,7 +37,7 @@ New Relic で何ができるか見てみましょう: * [Prometheus](/docs/infrastructure/prometheus-integrations/get-started/send-prometheus-metric-data-new-relic/#Agent)エージェントが提供するサービス検出機能を利用して、クラスタ内の任意のワークロードから Prometheus メトリックを取得します。 -* データに基づいて [アラートポリシー](/docs/alerts-applied-intelligence/new-relic-alerts/alert-policies/create-edit-or-find-alert-policy/) と[ アラート条件](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/alert-conditions/#create-alert-condition) Kubernetes[を作成するか、 定義済みのアラート条件](/docs/integrations/kubernetes-integration/kubernetes-events/kubernetes-integration-predefined-alert-policy) を拡張します。 +* データに基づいて [アラートポリシー](/docs/alerts-applied-intelligence/new-relic-alerts/alert-policies/create-edit-or-find-alert-policy/) と[ アラート条件](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/alert-conditions/#create-alert-condition) Kubernetes[を作成するか、 定義済みのアラート条件](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-prebuilt-alert-policies) を拡張します。 * すべての Kubernetes イベントを確認します。 [Kubernetesインテグレーション](/docs/integrations/kubernetes-integration/kubernetes-events/install-kubernetes-events-integration)は、 Kubernetesクラスタで発生するイベントを監視し、それらのイベントをNew Relicに送信します。 その後、クラスター エクスプローラーでイベント データを視覚化できます。 [New Relic Kubernetesインテグレーションをインストールする](/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-integration-install-configure/)とデフォルトでインストールされます。 diff --git a/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/kubernetes-integration-predefined-alert-policy.mdx b/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-prebuilt-alert-policies.mdx similarity index 100% rename from src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/kubernetes-integration-predefined-alert-policy.mdx rename to src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-prebuilt-alert-policies.mdx diff --git a/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-integration-recommended-alert-policy.mdx b/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-recommended-alert-policies.mdx similarity index 96% rename from src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-integration-recommended-alert-policy.mdx rename to src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-recommended-alert-policies.mdx index 1550154908e..ab70a5cd394 100644 --- a/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-integration-recommended-alert-policy.mdx +++ b/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-recommended-alert-policies.mdx @@ -8,7 +8,7 @@ freshnessValidatedDate: never translationType: machine --- -Kubernetesインテグレーションを初めてデプロイする際には、 [警告条件のデフォルトセット](/docs/alerts/new-relic-alerts/defining-conditions/define-alert-conditions) をお客様のアカウントにデプロイします。 [定義済みの警告ポリシー](/docs/integrations/kubernetes-integration/kubernetes-events/kubernetes-integration-predefined-alert-policy) 、お客様のKubernetesクラスタ上の警告条件の基礎となります。 +Kubernetesインテグレーションを初めてデプロイする際には、 [警告条件のデフォルトセット](/docs/alerts/new-relic-alerts/defining-conditions/define-alert-conditions) をお客様のアカウントにデプロイします。 [定義済みの警告ポリシー](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-prebuilt-alert-policies) 、お客様のKubernetesクラスタ上の警告条件の基礎となります。 すべての環境で最も一般的なユースケースに取り組むようにしていますが、デフォルトのポリシーを拡張するために設定できる追加のアラートも数多くあります。以下に、いくつかの推奨事項をご紹介します。 diff --git a/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/find-use-your-kubernetes-data.mdx b/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/find-use-your-kubernetes-data.mdx index e362f47783c..4aee886071c 100644 --- a/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/find-use-your-kubernetes-data.mdx +++ b/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/find-use-your-kubernetes-data.mdx @@ -9,25 +9,25 @@ freshnessValidatedDate: never translationType: machine --- -[独自の チャート](/docs/query-your-data/explore-query-data/use-charts/use-your-charts/) を構築し、 書き込み ビルダーと[ ](/docs/query-your-data/explore-query-data/get-started/introduction-querying-new-relic-data/)NerdGraph を使用して[Kubernetes インテグレーション](/docs/integrations/kubernetes-integration/get-started/introduction-kubernetes-integration)API データをすべて書き込むことができます。当社のインテグレーションは、インストゥルメント化されたコンテナ オーケストレーション レイヤーによってKubernetesデータを収集します。 +独自のチャートを作成したり、 [クエリ](/docs/using-new-relic/data/understand-data/query-new-relic-data) すべての [Kubernetesインテグレーション](/docs/integrations/kubernetes-integration/get-started/introduction-kubernetes-integration) データをクエリビルダやNerdGraph APIを使って照会することができます。当社の統合では、コンテナ・オーケストレーション・レイヤーをインスツルメンテーションすることでKubernetesのデータを収集します。よりシンプルで視覚的な体験をするには、 [クラスタエクスプローラ](/docs/integrations/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer) を使用してください。 -New Relic - Kubernetes dashboard +New Relic - Kubernetes dashboard
- **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Dashboards**に移動します。 [書き込みビルダー](/docs/chart-builder/use-chart-builder/get-started/introduction-chart-builder)を使用すると、 Kubernetesデータを作成し、明確な視覚化を作成できます。 + **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Dashboards**:[クエリビルダー](/docs/chart-builder/use-chart-builder/get-started/introduction-chart-builder)を使用すると、 Kubernetesデータをクエリし、明確な視覚化を作成できます。
- - Kubernetesデータを視覚的に確認したい場合は、[Kubernetesクラスタ エクスプローラー](/docs/integrations/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer)をご覧ください。 - - ## Kubernetesのデータを照会する [#view-data] [Kubernetesのデータを照会する最も簡単な方法](/docs/using-new-relic/data/understand-data/query-new-relic-data) は、 [クエリビルダー](/docs/query-your-data/explore-query-data/query-builder/use-advanced-nrql-mode-specify-data) を使用し、 [NRQLクエリ](/docs/query-data/nrql-new-relic-query-language/getting-started/introduction-nrql) を受け入れます。または、 [NerdGraph API](/docs/apis/nerdgraph/get-started/introduction-new-relic-nerdgraph) を使用してKubernetesデータを取得することもできます。 ### イベントと属性 [#event-types] -これらの[イベント](/docs/using-new-relic/data/understand-data/new-relic-data-types#event-data)には Kubernetes データが添付されます。 以下は Kubernetes の特定のイベントのリストです (このデータの詳細については、[データ ディクショナリ](/attribute-dictionary/?dataSource=Kubernetes)を参照してください)。 +Kubernetes データは次の[イベント](/docs/using-new-relic/data/understand-data/new-relic-data-types#event-data)に添付されます。このデータについて詳しくは、[データ ディクショナリ](/attribute-dictionary/?dataSource=Kubernetes)をご覧ください。 @@ -315,9 +315,11 @@ translationType: machine
+これらのイベントとその属性の詳細については、[データ ディクショナリ](/attribute-dictionary/?dataSource=Kubernetes)を参照してください。 + ### APMが監視するアプリケーションにおけるKubernetesのメタデータ [#apm-custom-attributes] -[アプリケーションをKubernetesに接続すると、](/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/link-apm-applications-kubernetes/)次のプロパティがアプリケーション データとディストリビューティッド（分散）トレーシング メタデータに追加されます。 +[アプリケーションをKubernetesと連携させることで](/docs/integrations/kubernetes-integration/metadata-injection/kubernetes-apm-metadata-injection) 、アプリケーショントレースや分散トレースに以下の属性が追加されます。 * `nodeName` * `containerName` @@ -326,10 +328,123 @@ translationType: machine * `deploymentName` * `namespaceName` -## 次のステップを選択 [#next-step] +## アラートの管理 [#alerts] + +Kubernetes データに関するとインシデントについて通知を受け取ることができます: + + + + Kubernetesインテグレーションのアラート条件を作成するには + + 1. **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure > Settings > Alerts > Kubernetes**に移動し、 **Create alert condition**を選択します。 + + 2. 選択した属性のみを持つKubernetesテンプレートに集計をフィルターするには、**Filter** を選択します。 + + 3. 閾値設定を選択します。 **Trigger an alert when...**オプションの詳細については、[集計タイプを](#alert-types)参照してください。 + + 4. 既存の [アラートポリシー](/docs/alerts/new-relic-alerts/configuring-alert-policies/create-or-rename-alert-policy) を選択するか、新しいポリシーを作成します。 + + 5. **Create**を選択します。 + + アラート条件の閾値がトリガーされると、New Relic はポリシーの通知チャンネルに [通知](#notifications) を送信します。 + + + + Kubernetesの統合には、独自のアラートポリシーとアラート条件が付属しています。定義済みのアラート条件を確認するには、 [Kubernetesの統合を参照してください。定義済みのアラートポリシー](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-prebuilt-alert-policies) をご覧ください。 + + さらに、Kubernetesインテグレーションを含め、使用している [New Relicインテグレーション](/docs/integrations/new-relic-integrations/getting-started/introduction-infrastructure-integrations) が収集するあらゆるメトリックに対してアラート条件を作成することができます。 + + 1. 集計タイプ + + + **Integrations** + + + を選択します。 + + 2. + **Select a data source** + + + ドロップダウンから、Kubernetes (K8s) データ ソースを選択します。 + + + + アラート条件の閾値がトリガーされると、New Relic はアラートポリシーで選択された通知チャンネルにメッセージを送信します。通知の種類に応じて、以下のようなオプションがあります。 + + * [インシデントを表示します](/docs/alerts-applied-intelligence/new-relic-alerts/alert-incidents/view-event-details-incidents)。 + + * [Acknowledge the incident](/docs/alerts/new-relic-alerts/reviewing-alert-incidents/acknowledge-alert-incidents). + + * 識別子名を選択すると、インシデントデータのチャートに移動します。 + + アラートを発生させたエンティティの識別子は、通知メッセージの先頭付近に表示されます。識別子の形式は、アラートの種類によって異なります。 + + * **Available pods are less than desired pods** アラート: + + ``` + K8s:CLUSTER_NAME:PARENT_NAMESPACE:replicaset:REPLICASET_NAME + ``` + + * **CPU or memory usage** アラート: + + ``` + K8s:CLUSTER_NAME:PARENT_NAMESPACE:POD_NAME:container:CONTAINER_NAME + ``` + + いくつか例を挙げてみましょう。 + + + + **Available pods are less than desired pods**アラートの場合、問題をトリガーする`ReplicaSet`の ID は次のようになります。 + + ``` + k8s:beam-production:default:replicaset:nginx-deployment-1623441481 + ``` + + この識別子には以下の情報が含まれています。 + + * クラスター名： `beam-production` + * 親名前空間： `default` + * `ReplicaSet` 名前： `nginx-deployment-1623441481` + + + + コンテナのCPUやメモリ使用量のアラートの場合、エンティティは次のようになります。 + + ``` + k8s:beam-production:kube-system:kube-state-metrics-797bb87c75-zncwn:container:kube-state-metrics + ``` + + この識別子には以下の情報が含まれています。 - - あなたのKubernetesイベントを見る + * クラスター名： `beam-production` + * 親名前空間： `kube-system` + * ポッド名前空間： `kube-state-metrics-797bb87c75-zncwn` + * コンテナ名： `kube-state-metrics` + + + - Kubernetesのデフォルトアラートポリシーを確認する - \ No newline at end of file + + 標準的な手順に従って、 [NRQL クエリのアラート条件を作成する](/docs/alerts/new-relic-alerts/defining-conditions/create-alert-conditions-nrql-queries) 。 + + diff --git a/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer.mdx b/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer.mdx index 62fdef17035..9273b945f0c 100644 --- a/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer.mdx +++ b/src/i18n/content/jp/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer.mdx @@ -253,7 +253,7 @@ Kubernetes 関連のエンティティについて学習するためのリソー New Relic - Cluster explorer -各ノードまたはポッドにマウスを合わせると、リソース使用量の概要が表示されます。各ノードとポッドをクリックして、時間の経過に伴うリソース使用量を表示したり、ヘルスとアクティブなアラートに関する詳細情報を取得したりできます。[色](/docs/alerts/new-relic-alerts/configuring-alert-policies/identify-entities-without-alert-policies)は[事前定義されたアラート条件](/docs/integrations/kubernetes-integration/kubernetes-events/kubernetes-integration-predefined-alert-policy)に基づいています。黄色のポッドにはアクティブな警告アラートがあり、赤いポッドにはアクティブなクリティカルアラートがあります。 +各ノードまたはポッドにマウスを合わせると、リソース使用量の概要が表示されます。各ノードとポッドをクリックして、時間の経過に伴うリソース使用量を表示したり、ヘルスとアクティブなアラートに関する詳細情報を取得したりできます。[色](/docs/alerts/new-relic-alerts/configuring-alert-policies/identify-entities-without-alert-policies)は[事前定義されたアラート条件](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-prebuilt-alert-policies)に基づいています。黄色のポッドにはアクティブな警告アラートがあり、赤いポッドにはアクティブなクリティカルアラートがあります。 New Relic - Cluster explorer - Pod alert diff --git a/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/windows-linux-hybrid-cluster.mdx b/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/windows-linux-hybrid-cluster.mdx index de5d7d1594e..23e727923c3 100644 --- a/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/windows-linux-hybrid-cluster.mdx +++ b/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/windows-linux-hybrid-cluster.mdx @@ -161,7 +161,7 @@ Kubernetes 데이터 탐색에 대해 자세히 알아보려면 다음 문서를 /> diff --git a/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration.mdx b/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration.mdx index 3c54ec7b5f3..88fd3a4ac82 100644 --- a/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration.mdx +++ b/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration.mdx @@ -37,7 +37,7 @@ Kubernetes를 관리하는 것은 어려울 수 있습니다. 몇 분 만에 컨 * [Prometheus 에이전트](/docs/infrastructure/prometheus-integrations/get-started/send-prometheus-metric-data-new-relic/#Agent) 가 제공하는 서비스 검색 덕분에 클러스터의 모든 워크로드에서 Prometheus 메트릭을 스크랩합니다. -* 데이터를 기반으로 [공지 사항](/docs/alerts-applied-intelligence/new-relic-alerts/alert-policies/create-edit-or-find-alert-policy/) 및 [공지 조건을](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/alert-conditions/#create-alert-condition) 생성하거나 사전 정의된 Kubernetes [공지 조건을 확장합니다.](/docs/integrations/kubernetes-integration/kubernetes-events/kubernetes-integration-predefined-alert-policy) +* 데이터를 기반으로 [공지 사항](/docs/alerts-applied-intelligence/new-relic-alerts/alert-policies/create-edit-or-find-alert-policy/) 및 [공지 조건을](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/alert-conditions/#create-alert-condition) 생성하거나 사전 정의된 Kubernetes [공지 조건을 확장합니다.](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-prebuilt-alert-policies) * 모든 Kubernetes 이벤트를 확인하세요. [Kubernetes 이벤트 통합은](/docs/integrations/kubernetes-integration/kubernetes-events/install-kubernetes-events-integration) 쿠버네티스 클러스터에서 발생하는 이벤트를 감시하고 해당 이벤트를 뉴렐릭으로 보냅니다. 그런 다음 클러스터 탐색기에서 이벤트 데이터를 시각화할 수 있습니다. [뉴렐릭 Kubernetes 통합 설치](/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-integration-install-configure/) 후 기본으로 설치됩니다. diff --git a/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/kubernetes-integration-predefined-alert-policy.mdx b/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-prebuilt-alert-policies.mdx similarity index 100% rename from src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/kubernetes-integration-predefined-alert-policy.mdx rename to src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-prebuilt-alert-policies.mdx diff --git a/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-integration-recommended-alert-policy.mdx b/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-recommended-alert-policies.mdx similarity index 95% rename from src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-integration-recommended-alert-policy.mdx rename to src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-recommended-alert-policies.mdx index 3e8f3dde5bc..fc08f43e9db 100644 --- a/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-integration-recommended-alert-policy.mdx +++ b/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-recommended-alert-policies.mdx @@ -8,7 +8,7 @@ freshnessValidatedDate: never translationType: machine --- -Kubernetes 통합을 처음 배포할 때 Kubernetes 클러스터의 경고 조건에 대한 기반인 [사전 정의된 경고 정책](/docs/integrations/kubernetes-integration/kubernetes-events/kubernetes-integration-predefined-alert-policy) 인 기본 [경고 조건](/docs/alerts/new-relic-alerts/defining-conditions/define-alert-conditions) 세트를 계정에 배포합니다. +Kubernetes 통합을 처음 배포할 때 Kubernetes 클러스터의 경고 조건에 대한 기반인 [사전 정의된 경고 정책](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-prebuilt-alert-policies) 인 기본 [경고 조건](/docs/alerts/new-relic-alerts/defining-conditions/define-alert-conditions) 세트를 계정에 배포합니다. 모든 환경에서 가장 일반적인 사용 사례를 해결하려고 노력하는 동안 기본 정책을 확장하기 위해 설정할 수 있는 추가 경고가 많이 있습니다. 다음은 몇 가지 권장 사항입니다. diff --git a/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/find-use-your-kubernetes-data.mdx b/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/find-use-your-kubernetes-data.mdx index cde79e8d21c..39b879a891e 100644 --- a/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/find-use-your-kubernetes-data.mdx +++ b/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/find-use-your-kubernetes-data.mdx @@ -9,25 +9,25 @@ freshnessValidatedDate: never translationType: machine --- -쿼리 빌더와 NerdGraph API를 사용하여 나만의 차트를 만들고 모든 [](/docs/query-your-data/explore-query-data/use-charts/use-your-charts/)[Kubernetes](/docs/integrations/kubernetes-integration/get-started/introduction-kubernetes-integration) 통합 데이터를 쿼리 [할 수 있습니다.](/docs/query-your-data/explore-query-data/get-started/introduction-querying-new-relic-data/) 우리의 통합은 컨테이너 오케스트레이션 계층을 통해 Kubernetes 데이터를 수집합니다. +쿼리 빌더와 NerdGraph API를 사용하여 자체 차트를 만들고 모든[Kubernetes 통합](/docs/integrations/kubernetes-integration/get-started/introduction-kubernetes-integration) 데이터를 [쿼리](/docs/using-new-relic/data/understand-data/query-new-relic-data) 할 수 있습니다. 우리의 통합은 컨테이너 오케스트레이션 계층을 계측하여 Kubernetes 데이터를 수집합니다. 더 간단하고 시각적인 경험을 위해[클러스터 탐색기](/docs/integrations/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer) 를 사용하십시오. -New Relic - Kubernetes dashboard +New Relic - Kubernetes dashboard
- **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Dashboards** 로 이동합니다. [쿼리 빌더를](/docs/chart-builder/use-chart-builder/get-started/introduction-chart-builder) 사용하면 Kubernetes 데이터를 쿼리하고 명확한 시각화를 만들 수 있습니다. + **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Dashboards**: [쿼리 빌더를](/docs/chart-builder/use-chart-builder/get-started/introduction-chart-builder) 사용하면 Kubernetes 데이터를 쿼리하고 명확한 시각화를 생성할 수 있습니다.
- - Kubernetes 데이터의 시각적 경험을 선호한다면 [쿠버네티스 클러스터 탐색기를](/docs/integrations/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer) 참조하세요. - - ## Kubernetes 데이터 쿼리 [#view-data] [Kubernetes 데이터를 쿼리](/docs/using-new-relic/data/understand-data/query-new-relic-data) 하는 가장 간단한 방법은 [NRQL 쿼리](/docs/query-data/nrql-new-relic-query-language/getting-started/introduction-nrql) 를 수락하는 [쿼리 빌더](/docs/query-your-data/explore-query-data/query-builder/use-advanced-nrql-mode-specify-data) 를 사용하는 것입니다. 또는 [NerdGraph API](/docs/apis/nerdgraph/get-started/introduction-new-relic-nerdgraph) 를 사용하여 Kubernetes 데이터를 검색할 수 있습니다. ### 이벤트 및 속성 [#event-types] -이러한 [이벤트](/docs/using-new-relic/data/understand-data/new-relic-data-types#event-data) 에는 Kubernetes 데이터가 첨부됩니다. 다음은 Kubernetes에 대한 특정 이벤트 목록입니다( [데이터 사전](/attribute-dictionary/?dataSource=Kubernetes) 에서 이 데이터에 대해 자세히 알아보세요). +쿠버네티스 데이터는 다음 [이벤트](/docs/using-new-relic/data/understand-data/new-relic-data-types#event-data)에 연결됩니다. [뉴렐릭의 데이터 사전](/attribute-dictionary/?dataSource=Kubernetes)에서 이 데이터에 대해 자세히 알아볼 수 있습니다. @@ -315,9 +315,11 @@ translationType: machine
+이러한 이벤트와 그 속성에 대해 자세히 알아보려면 [데이터 사전](/attribute-dictionary/?dataSource=Kubernetes)을 참조하십시오. + ### APM 모니터링 애플리케이션의 Kubernetes 메타데이터 [#apm-custom-attributes] -[Kubernetes에 연결하면](/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/link-apm-applications-kubernetes/) 다음과 같은 속성이 귀하의 특수 데이터는 물론이고 내보내고 싶은 데이터에 추가됩니다. +[애플리케이션을 Kubernetes와 연결](/docs/integrations/kubernetes-integration/metadata-injection/kubernetes-apm-metadata-injection) 하면 애플리케이션 추적 및 분산 추적에 다음 속성이 추가됩니다. * `nodeName` * `containerName` @@ -326,10 +328,123 @@ translationType: machine * `deploymentName` * `namespaceName` -## 다음 단계 선택 [#next-step] +## 알림 관리 [#alerts] + +Kubernetes 데이터에 대한 및 인시던트에 대한 알림을 받을 수 있습니다. + + + + Kubernetes 통합에 대한 경고 조건을 생성하려면 다음 안내를 따르세요. + + 1. **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure > Settings > Alerts > Kubernetes** 로 이동한 다음 **Create alert condition** 선택합니다. + + 2. 선택한 속성만 있는 Kubernetes 티에 대한 공지를 필터링하려면 **Filter**을 선택합니다. + + 3. 청년값, 릴레이 설정을 선택하세요. **Trigger an alert when...** 옵션에 대한 자세한 내용은 [공지 유형을](#alert-types) 참조하세요. + + 4. 기존 [알림 정책](/docs/alerts/new-relic-alerts/configuring-alert-policies/create-or-rename-alert-policy) 을 선택하거나 새 알림 정책을 만듭니다. + + 5. **Create** 선택합니다. + + 경고 조건의 임계값이 트리거되면 New Relic은 정책의 알림 채널에 [알림](#notifications) 을 보냅니다. + + + + Kubernetes 통합은 자체 경고 정책 및 경고 조건과 함께 제공됩니다. 사전 정의된 경고 조건이 무엇인지 보려면 [Kubernetes 통합: 사전 정의된 경고 정책](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-prebuilt-alert-policies) 을 참조하십시오. + + 또한 Kubernetes 통합을 포함하여 사용하는 [New Relic 통합에서](/docs/integrations/new-relic-integrations/getting-started/introduction-infrastructure-integrations) 수집한 모든 메트릭에 대한 경고 조건을 생성할 수 있습니다. + + 1. 공지 유형 + + + **Integrations** + + + 을 선택합니다. + + 2. + **Select a data source** + + + 드롭다운 메뉴에서 Kubernetes (K8s) 데이터 소스를 선택하세요. + + + + 경고 조건의 임계값이 트리거되면 New Relic은 경고 정책에서 선택한 알림 채널로 메시지를 보냅니다. 알림 유형에 따라 다음과 같은 옵션이 있을 수 있습니다. + + * [인시던트를 확인합니다](/docs/alerts-applied-intelligence/new-relic-alerts/alert-incidents/view-event-details-incidents). + + * [사건을 인정하십시오](/docs/alerts/new-relic-alerts/reviewing-alert-incidents/acknowledge-alert-incidents) . + + * 식별자 이름을 선택하여 사고 데이터 차트로 이동합니다. + + 경고를 트리거한 엔터티 식별자는 알림 메시지 상단 근처에 나타납니다. 식별자 형식은 경고 유형에 따라 다릅니다. + + * **Available pods are less than desired pods** 알림: + + ``` + K8s:CLUSTER_NAME:PARENT_NAMESPACE:replicaset:REPLICASET_NAME + ``` + + * **CPU or memory usage** 알림: + + ``` + K8s:CLUSTER_NAME:PARENT_NAMESPACE:POD_NAME:container:CONTAINER_NAME + ``` + + 여기 예시들이 있습니다. + + + + **Available pods are less than desired pods** 알림의 경우 문제를 유발하는 `ReplicaSet` 의 ID는 다음과 같습니다. + + ``` + k8s:beam-production:default:replicaset:nginx-deployment-1623441481 + ``` + + 이 식별자에는 다음 정보가 포함됩니다. + + * 클러스터 이름: `beam-production` + * 상위 네임스페이스: `default` + * `ReplicaSet` 이름: `nginx-deployment-1623441481` + + + + 컨테이너 CPU 또는 메모리 사용량 경고의 경우 엔터티는 다음과 같을 수 있습니다. + + ``` + k8s:beam-production:kube-system:kube-state-metrics-797bb87c75-zncwn:container:kube-state-metrics + ``` + + 이 식별자에는 다음 정보가 포함됩니다. - - Kubernetes 이벤트 보기 + * 클러스터 이름: `beam-production` + * 상위 네임스페이스: `kube-system` + * 포드 네임스페이스: `kube-state-metrics-797bb87c75-zncwn` + * 컨테이너 이름: `kube-state-metrics` + + + - Kubernetes 기본 공지를 확인하세요. - \ No newline at end of file + + [NRQL 쿼리에 대한 경고 조건을 생성](/docs/alerts/new-relic-alerts/defining-conditions/create-alert-conditions-nrql-queries) 하려면 표준 절차를 따르십시오. + + diff --git a/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer.mdx b/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer.mdx index b75e6c9f7a4..6940a41f49d 100644 --- a/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer.mdx +++ b/src/i18n/content/kr/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer.mdx @@ -253,7 +253,7 @@ Kubernetes 관련 엔터티에 대해 알아보기 위한 몇 가지 리소스: New Relic - Cluster explorer -리소스 사용량에 대한 빠른 개요를 보려면 각 노드 또는 포드 위로 마우스를 가져갑니다. 각 노드와 포드를 클릭하여 시간 경과에 따른 리소스 사용량을 보거나 상태 및 활성 경고에 대한 추가 정보를 얻을 수 있습니다. [색상](/docs/alerts/new-relic-alerts/configuring-alert-policies/identify-entities-without-alert-policies) 은 [사전 정의된 경고 조건](/docs/integrations/kubernetes-integration/kubernetes-events/kubernetes-integration-predefined-alert-policy) 을 기반으로 합니다. 노란색 포드에는 활성 경고 경고가 있고 빨간색 포드에는 활성 위험 경고가 있습니다. +리소스 사용량에 대한 빠른 개요를 보려면 각 노드 또는 포드 위로 마우스를 가져갑니다. 각 노드와 포드를 클릭하여 시간 경과에 따른 리소스 사용량을 보거나 상태 및 활성 경고에 대한 추가 정보를 얻을 수 있습니다. [색상](/docs/alerts/new-relic-alerts/configuring-alert-policies/identify-entities-without-alert-policies) 은 [사전 정의된 경고 조건](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-prebuilt-alert-policies) 을 기반으로 합니다. 노란색 포드에는 활성 경고 경고가 있고 빨간색 포드에는 활성 위험 경고가 있습니다. New Relic - Cluster explorer - Pod alert diff --git a/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/windows-linux-hybrid-cluster.mdx b/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/windows-linux-hybrid-cluster.mdx index 37076dff70b..02df625331a 100644 --- a/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/windows-linux-hybrid-cluster.mdx +++ b/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/windows-linux-hybrid-cluster.mdx @@ -161,7 +161,7 @@ Para saber mais sobre como explorar seus dados do Kubernetes, confira estes docu /> diff --git a/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration.mdx b/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration.mdx index a3f5a31dc36..d074daed710 100644 --- a/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration.mdx +++ b/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/get-started/introduction-kubernetes-integration.mdx @@ -37,7 +37,7 @@ Dê uma olhada no que você pode fazer com o New Relic: * Extraia métricas do Prometheus de qualquer workload no cluster graças à descoberta de serviço fornecida pelo [agente Prometheus](/docs/infrastructure/prometheus-integrations/get-started/send-prometheus-metric-data-new-relic/#Agent). -* Crie [política de alertas](/docs/alerts-applied-intelligence/new-relic-alerts/alert-policies/create-edit-or-find-alert-policy/) e [condição do alerta](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/alert-conditions/#create-alert-condition) com base nos dados do Kubernetes ou estenda a [condição do alerta predefinida](/docs/integrations/kubernetes-integration/kubernetes-events/kubernetes-integration-predefined-alert-policy). +* Crie [política de alertas](/docs/alerts-applied-intelligence/new-relic-alerts/alert-policies/create-edit-or-find-alert-policy/) e [condição do alerta](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/alert-conditions/#create-alert-condition) com base nos dados do Kubernetes ou estenda a [condição do alerta predefinida](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-prebuilt-alert-policies). * Confira todos os seus eventos Kubernetes . A [integração de eventosKubernetes ](/docs/integrations/kubernetes-integration/kubernetes-events/install-kubernetes-events-integration)monitora os eventos que acontecem no seu cluster do Kubernetes e os envia para o New Relic. Você pode então visualizar os dados do evento no cluster Explorer. Ele é instalado por padrão após [a instalação da integração do New Relic Kubernetes](/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-integration-install-configure/). diff --git a/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/kubernetes-integration-predefined-alert-policy.mdx b/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-prebuilt-alert-policies.mdx similarity index 100% rename from src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/kubernetes-integration-predefined-alert-policy.mdx rename to src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-prebuilt-alert-policies.mdx diff --git a/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-integration-recommended-alert-policy.mdx b/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-recommended-alert-policies.mdx similarity index 96% rename from src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-integration-recommended-alert-policy.mdx rename to src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-recommended-alert-policies.mdx index e0fc621e0dc..4004937172a 100644 --- a/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-integration-recommended-alert-policy.mdx +++ b/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-recommended-alert-policies.mdx @@ -8,7 +8,7 @@ freshnessValidatedDate: never translationType: machine --- -Ao implantar a integração Kubernetes pela primeira vez, implantamos um conjunto padrão de [condição do alerta](/docs/alerts/new-relic-alerts/defining-conditions/define-alert-conditions) em sua conta, a [política de alertas predefinida](/docs/integrations/kubernetes-integration/kubernetes-events/kubernetes-integration-predefined-alert-policy), uma base para condição do alerta em seu cluster do Kubernetes. +Ao implantar a integração Kubernetes pela primeira vez, implantamos um conjunto padrão de [condição do alerta](/docs/alerts/new-relic-alerts/defining-conditions/define-alert-conditions) em sua conta, a [política de alertas predefinida](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-prebuilt-alert-policies), uma base para condição do alerta em seu cluster do Kubernetes. Embora tentemos abordar os casos de uso mais comuns em todos os ambientes, há vários alertas adicionais que você pode configurar para estender a política padrão. A seguir estão algumas recomendações. diff --git a/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/find-use-your-kubernetes-data.mdx b/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/find-use-your-kubernetes-data.mdx index 2463979b207..5a07ec56a88 100644 --- a/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/find-use-your-kubernetes-data.mdx +++ b/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/find-use-your-kubernetes-data.mdx @@ -9,25 +9,25 @@ freshnessValidatedDate: never translationType: machine --- -Você pode criar seus próprios [gráficos](/docs/query-your-data/explore-query-data/use-charts/use-your-charts/) e [consultar](/docs/query-your-data/explore-query-data/get-started/introduction-querying-new-relic-data/) todos os seus dados [de integração Kubernetes ](/docs/integrations/kubernetes-integration/get-started/introduction-kubernetes-integration)usando o criador de consulta e a API NerdGraph. Nossa integração coleta dados Kubernetes instrumentando a camada de orquestração do contêiner. +Você pode construir seus próprios gráficos e [consultar](/docs/using-new-relic/data/understand-data/query-new-relic-data) todos os seus dados [de integração Kubernetes ](/docs/integrations/kubernetes-integration/get-started/introduction-kubernetes-integration)usando o criador de consulta e a API NerdGraph. Nossa integração coleta dados Kubernetes instrumentando a camada de orquestração do contêiner. Para uma experiência mais simples e visual, use o [cluster explorer](/docs/integrations/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer). -New Relic - Kubernetes dashboard +New Relic - Kubernetes dashboard
- Vá para **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Dashboards**. Usando o [criador de consulta](/docs/chart-builder/use-chart-builder/get-started/introduction-chart-builder) você pode consultar seus dados Kubernetes e criar visualizações claras. + **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Dashboards**: Usando o [criador de consulta](/docs/chart-builder/use-chart-builder/get-started/introduction-chart-builder) você pode consultar seus dados Kubernetes e criar visualizações claras.
- - Se você preferir uma experiência visual dos seus dados do Kubernetes, consulte nosso [explorador de cluster do Kubernetes](/docs/integrations/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer). - - ## Consultar dados Kubernetes [#view-data] A forma mais simples de [consultar seus dados Kubernetes ](/docs/using-new-relic/data/understand-data/query-new-relic-data)é utilizando o [criador de consulta](/docs/query-your-data/explore-query-data/query-builder/use-advanced-nrql-mode-specify-data), que aceita [consultaNRQL ](/docs/query-data/nrql-new-relic-query-language/getting-started/introduction-nrql). Alternativamente, você pode usar a [API NerdGraph](/docs/apis/nerdgraph/get-started/introduction-new-relic-nerdgraph) para recuperar dados do Kubernetes. ### Evento e atributo [#event-types] -Os dados Kubernetes são anexados a esses [eventos](/docs/using-new-relic/data/understand-data/new-relic-data-types#event-data). Aqui está uma lista de eventos específicos para Kubernetes (saiba mais sobre esses dados em [nosso dicionário de dados](/attribute-dictionary/?dataSource=Kubernetes)). +Os dados Kubernetes são anexados ao seguinte [evento](/docs/using-new-relic/data/understand-data/new-relic-data-types#event-data). Você pode aprender mais sobre esses dados em [nosso dicionário de dados](/attribute-dictionary/?dataSource=Kubernetes). @@ -315,9 +315,11 @@ Os dados Kubernetes são anexados a esses [eventos](/docs/using-new-relic/data/u
+Para saber mais sobre esses eventos e seus atributos, consulte [nosso dicionário de dados](/attribute-dictionary/?dataSource=Kubernetes). + ### Metadados Kubernetes no aplicativo APM-monitor [#apm-custom-attributes] -[Conectar seu aplicativo ao Kubernetes](/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/link-apm-applications-kubernetes/) adiciona estes atributos aos dados do seu aplicativo, bem como ao distributed tracing de metadados: +[Ao vincular seu aplicativo ao Kubernetes](/docs/integrations/kubernetes-integration/metadata-injection/kubernetes-apm-metadata-injection), os seguintes atributos são adicionados ao trace do aplicativo e distributed trace: * `nodeName` * `containerName` @@ -326,10 +328,125 @@ Os dados Kubernetes são anexados a esses [eventos](/docs/using-new-relic/data/u * `deploymentName` * `namespaceName` -## Escolha seu próximo passo [#next-step] +## Gerenciar alertas [#alerts] + +Você pode ser notificado sobre um incidente relacionado aos seus dados Kubernetes : + + + + Para criar uma condição do alerta para a integração do Kubernetes : + + 1. Vá para **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure > Settings > Alerts > Kubernetes** e selecione **Create alert condition**. + + 2. Para filtrar o alerta para a entidade Kubernetes que possui apenas o atributo escolhido, selecione **Filter**. + + 3. Selecione as configurações de limite. Para obter mais informações sobre as opções **Trigger an alert when...** , consulte [Tipos de alerta](#alert-types). + + 4. Selecione uma [política de alertas](/docs/alerts/new-relic-alerts/configuring-alert-policies/create-or-rename-alert-policy) existente ou crie uma nova. + + 5. Selecione **Create**. + + Quando o limite de condição do alerta é acionado, New Relic envia uma [notificação](#notifications) para o canal de notificação da apólice. + + + + A integração Kubernetes vem com sua própria política de alertas e condição do alerta. Para ver quais são as condições de alerta predefinidas, consulte [Integração Kubernetes : política de alertas predefinida](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-prebuilt-alert-policies). + + Além disso, você pode criar uma condição do alerta para qualquer métrica coletada por qualquer [integração New Relic ](/docs/integrations/new-relic-integrations/getting-started/introduction-infrastructure-integrations)que você usar, incluindo a integração Kubernetes : + + 1. Selecione o tipo de alerta + + + **Integrations** + + + . + + 2. No dropdown + + + **Select a data source** + + + , selecione uma fonte de dados Kubernetes (K8s). + + + + Quando o limite de condição de alerta é acionado, New Relic envia uma mensagem para o(s) canal(es) de notificação escolhido(s) na política de alertas. Dependendo do tipo de notificação, você poderá ter as seguintes opções: + + * [Veja o incidente](/docs/alerts-applied-intelligence/new-relic-alerts/alert-incidents/view-event-details-incidents). + + * [Reconheça o incidente](/docs/alerts/new-relic-alerts/reviewing-alert-incidents/acknowledge-alert-incidents). + + * Acesse um gráfico dos dados do incidente selecionando o nome do identificador. + + O identificador da entidade que acionou o alerta aparece próximo ao topo da mensagem de notificação. O formato do identificador depende do tipo de alerta: + + * **Available pods are less than desired pods** alertas: + + ``` + K8s:CLUSTER_NAME:PARENT_NAMESPACE:replicaset:REPLICASET_NAME + ``` + + * **CPU or memory usage** alertas: + + ``` + K8s:CLUSTER_NAME:PARENT_NAMESPACE:POD_NAME:container:CONTAINER_NAME + ``` + + Aqui estão alguns exemplos. + + + + Para alertas **Available pods are less than desired pods** , o ID do `ReplicaSet` que aciona o problema pode ser semelhante a este: + + ``` + k8s:beam-production:default:replicaset:nginx-deployment-1623441481 + ``` + + Este identificador contém as seguintes informações: + + * Nome do cluster: `beam-production` + * Namespace pai: `default` + * `ReplicaSet` nome: `nginx-deployment-1623441481` + + + + Para alertas de uso de CPU ou memória do contêiner, a entidade pode ter esta aparência: + + ``` + k8s:beam-production:kube-system:kube-state-metrics-797bb87c75-zncwn:container:kube-state-metrics + ``` + + Este identificador contém as seguintes informações: - - Veja seu evento Kubernetes + * Nome do cluster: `beam-production` + * Namespace pai: `kube-system` + * Pod namespace: `kube-state-metrics-797bb87c75-zncwn` + * Nome do contêiner: `kube-state-metrics` + + + - Verifique nossa política de alertas padrão Kubernetes - \ No newline at end of file + + Siga os procedimentos padrão para [criar a condição do alerta para consulta NRQL ](/docs/alerts/new-relic-alerts/defining-conditions/create-alert-conditions-nrql-queries). + + diff --git a/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer.mdx b/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer.mdx index cac011182ed..f54f75d56a9 100644 --- a/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer.mdx +++ b/src/i18n/content/pt/docs/kubernetes-pixie/kubernetes-integration/understand-use-data/kubernetes-cluster-explorer.mdx @@ -253,7 +253,7 @@ O explorador de cluster representa os dados de cluster mais relevantes em um gr New Relic - Cluster explorer -Passe o mouse sobre cada nó ou pod para obter uma visão geral rápida do uso de recursos. Você pode clicar em cada nó e pod para visualizar o uso de recursos ao longo do tempo ou para obter mais informações sobre seu funcionamento e alertas ativos. [As cores](/docs/alerts/new-relic-alerts/configuring-alert-policies/identify-entities-without-alert-policies) são baseadas na [condição do alerta predefinida](/docs/integrations/kubernetes-integration/kubernetes-events/kubernetes-integration-predefined-alert-policy): o pod amarelo possui alertas de aviso ativos, enquanto o pod vermelho possui alerta crítico ativo. +Passe o mouse sobre cada nó ou pod para obter uma visão geral rápida do uso de recursos. Você pode clicar em cada nó e pod para visualizar o uso de recursos ao longo do tempo ou para obter mais informações sobre seu funcionamento e alertas ativos. [As cores](/docs/alerts/new-relic-alerts/configuring-alert-policies/identify-entities-without-alert-policies) são baseadas na [condição do alerta predefinida](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-prebuilt-alert-policies): o pod amarelo possui alertas de aviso ativos, enquanto o pod vermelho possui alerta crítico ativo. New Relic - Cluster explorer - Pod alert diff --git a/src/install/config/kubernetes.yaml b/src/install/config/kubernetes.yaml index 918e55e4e00..136b1113a4f 100644 --- a/src/install/config/kubernetes.yaml +++ b/src/install/config/kubernetes.yaml @@ -68,4 +68,5 @@ steps: options: - value: 'manifest' - filePath: 'src/install/kubernetes/find-data.mdx' + - filePath: 'src/install/kubernetes/prebuilt-resources.mdx' whatsNextFilePath: 'src/install/kubernetes/whatsNext.mdx' \ No newline at end of file diff --git a/src/install/kubernetes/find-data.mdx b/src/install/kubernetes/find-data.mdx index 7616ee6ed51..c930af7540a 100644 --- a/src/install/kubernetes/find-data.mdx +++ b/src/install/kubernetes/find-data.mdx @@ -26,38 +26,3 @@ After the installation, you should see the following in the UI: * `prometheus-agent` pod, if you enabled the [Prometheus agent](/docs/infrastructure/prometheus-integrations/install-configure-prometheus-agent/install-prometheus-agent) integration. * `newrelic-newrelic-logging` pod for each node in your cluster, if you enabled the logging integration. - - - 1. Go to **[one.newrelic.com](https://one.newrelic.com) > +Integrations & Agents** and type **Kubernetes**. - - 2. Under **Dashboards**, click **Kubernetes**. - - Add Kubernetes dashboards - - 3. Click **Edit** if you want to change the account in the popup window that opens. - - 4. Click **Setup Kubernetes** or **Skip this step** if you already setup this datasource. - - 5. Click **View dashboard**, and see your Kubernetes data in New Relic. - - - - 1. Go to **[one.newrelic.com](https://one.newrelic.com) > +Integrations & Agents** and type **Kubernetes**. - - For more on creating alerts, see our [alert conditions](/docs/alerts/create-alert/create-alert-condition/alert-conditions/) doc. - - - - - If you install the integration through the [New Relic Kubernetes quickstart](https://newrelic.com/instant-observability/kubernetes) you'll have pre-built resources like a dashboard, instrumentation, and 23 alerts. - diff --git a/src/install/kubernetes/prebuilt-resources.mdx b/src/install/kubernetes/prebuilt-resources.mdx new file mode 100644 index 00000000000..a6909bca9f1 --- /dev/null +++ b/src/install/kubernetes/prebuilt-resources.mdx @@ -0,0 +1,30 @@ +--- +componentType: default +headingText: (Optional) Add pre-built resources +--- + +After deploying this integration, you can add these pre-built resources: + +* A default **set of pre-built alert policies**. This is a default set of recommended alerts conditions that you can add to your account. These conditions are grouped into a policy called **Kubernetes alert policy**. Once added, you can customize the [alert conditions](/docs/alerts/create-alert/create-alert-condition/alert-conditions/) to meet your needs. See [Recommended alert policies](/docs/kubernetes-pixie/kubernetes-integration/installation/recommended-alert-policies) for more information about managing them. + +* **Pre-built dasboards**. Follow these steps to add pre-defined dashboards: + + 1. Go to **[one.newrelic.com](https://one.newrelic.com) > + Integrations & Agents**. + + 2. Select **Dashboards** to access the pre-built resources. + + 3. Search **Kubernetes** and select the dashboard you want to add. + + Add Kubernetes dashboards + + 4. Click **Edit** if you want to change the account in the popup window that opens. + + 5. Click **Setup Kubernetes** or **Skip this step** if you already setup this datasource. + + 6. Click **View dashboard**, and see your Kubernetes data in New Relic. + + For more on creating dasboards, see our [Create custom data visualizations with dashboards](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/) doc. diff --git a/src/nav/kubernetes-pixie.yml b/src/nav/kubernetes-pixie.yml index af77e2d5f6b..1ca5624d379 100644 --- a/src/nav/kubernetes-pixie.yml +++ b/src/nav/kubernetes-pixie.yml @@ -17,12 +17,18 @@ pages: path: /docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-windows - title: Upgrade the Kubernetes integration path: /docs/kubernetes-pixie/kubernetes-integration/installation/upgrading-kubernetes - - title: Uninstall Kubernetes integration - path: /docs/kubernetes-pixie/kubernetes-integration/installation/uninstall-kubernetes - title: Reduce data ingested path: /docs/kubernetes-pixie/kubernetes-integration/installation/reduce-ingest - title: Kubernetes agent operator path: /docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator + - title: Manage Kubernetes alerts + pages: + - title: Predefined alert policy + path: /docs/kubernetes-pixie/kubernetes-integration/installation/predefined-alert-policy + - title: Recommended alert policy + path: /docs/kubernetes-pixie/kubernetes-integration/installation/recommended-alert-policy + - title: Create and modify Kubernetes alerts + path: /docs/kubernetes-pixie/kubernetes-integration/installation/create-alerts - title: Link APM-instrumented apps to Kubernetes path: /docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/link-apm-applications-kubernetes - title: Link OTel-instrumented apps to Kubernetes @@ -58,7 +64,9 @@ pages: - title: Errors for v2 path: /docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/k8s-version2/errors - title: "Troubleshooting v2: Missing nodes" - path: /docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/k8s-version2/troubleshooting + path: /docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/k8s-version2/troubleshooting + - title: Uninstall Kubernetes integration + path: /docs/kubernetes-pixie/kubernetes-integration/installation/uninstall-kubernetes - title: Explore your Kubernetes data pages: - title: Kubernetes cluster @@ -69,12 +77,6 @@ pages: path: /docs/kubernetes-pixie/kubernetes-integration/understand-use-data/kubernetes-events-integration - title: Plugin for log forwarding path: /docs/logs/forward-logs/kubernetes-plugin-log-forwarding - - title: Set alerts on Kubernetes - pages: - - title: Predefined alert policy - path: /docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/kubernetes-integration-predefined-alert-policy - - title: Recommended alerts - path: /docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-integration-recommended-alert-policy - title: Troubleshooting pages: - title: Not seeing data diff --git a/static/images/kubernetes_screenshot-crop_add-alerts.webp b/static/images/kubernetes_screenshot-crop_add-alerts.webp index 6e221d6d301..5910c774049 100644 Binary files a/static/images/kubernetes_screenshot-crop_add-alerts.webp and b/static/images/kubernetes_screenshot-crop_add-alerts.webp differ diff --git a/static/images/kubernetes_screenshot-crop_add-dashboards.webp b/static/images/kubernetes_screenshot-crop_add-dashboards.webp index cc6c4f78eb4..d2792249052 100644 Binary files a/static/images/kubernetes_screenshot-crop_add-dashboards.webp and b/static/images/kubernetes_screenshot-crop_add-dashboards.webp differ diff --git a/static/images/kubernetes_screenshot-crop_create_alert_condition.webp b/static/images/kubernetes_screenshot-crop_create_alert_condition.webp new file mode 100644 index 00000000000..795e801a77f Binary files /dev/null and b/static/images/kubernetes_screenshot-crop_create_alert_condition.webp differ diff --git a/static/images/kubernetes_screenshot-crop_create_alert_policy.webp b/static/images/kubernetes_screenshot-crop_create_alert_policy.webp new file mode 100644 index 00000000000..8bc15e6183d Binary files /dev/null and b/static/images/kubernetes_screenshot-crop_create_alert_policy.webp differ diff --git a/static/images/kubernetes_screenshot-crop_default-alert-policy.webp b/static/images/kubernetes_screenshot-crop_default-alert-policy.webp new file mode 100644 index 00000000000..5c2b2dbe5e4 Binary files /dev/null and b/static/images/kubernetes_screenshot-crop_default-alert-policy.webp differ diff --git a/static/images/kubernetes_screenshot-crop_new-alert-condition-button.webp b/static/images/kubernetes_screenshot-crop_new-alert-condition-button.webp new file mode 100644 index 00000000000..19eed579db2 Binary files /dev/null and b/static/images/kubernetes_screenshot-crop_new-alert-condition-button.webp differ diff --git a/static/images/kubernetes_screenshot-crop_new-alert-policy-button.webp b/static/images/kubernetes_screenshot-crop_new-alert-policy-button.webp new file mode 100644 index 00000000000..6908d4af207 Binary files /dev/null and b/static/images/kubernetes_screenshot-crop_new-alert-policy-button.webp differ diff --git a/static/images/kubernetes_screenshot-crop_pre-built-resources.webp b/static/images/kubernetes_screenshot-crop_pre-built-resources.webp new file mode 100644 index 00000000000..d03e5d774fc Binary files /dev/null and b/static/images/kubernetes_screenshot-crop_pre-built-resources.webp differ diff --git a/static/images/kubernetes_screenshot-crop_recommended-alert-policies.webp b/static/images/kubernetes_screenshot-crop_recommended-alert-policies.webp new file mode 100644 index 00000000000..dfa968dd06e Binary files /dev/null and b/static/images/kubernetes_screenshot-crop_recommended-alert-policies.webp differ diff --git a/static/images/whats-new-signal-loss-standalone.webp b/static/images/whats-new-signal-loss-standalone.webp new file mode 100644 index 00000000000..869b2ef4016 Binary files /dev/null and b/static/images/whats-new-signal-loss-standalone.webp differ