diff --git a/src/content/docs/alerts/admin/rules-limits-alerts.mdx b/src/content/docs/alerts/admin/rules-limits-alerts.mdx
index 64c08a56282..8e8663e24d0 100644
--- a/src/content/docs/alerts/admin/rules-limits-alerts.mdx
+++ b/src/content/docs/alerts/admin/rules-limits-alerts.mdx
@@ -151,7 +151,7 @@ Limits and rules pertaining to New Relic :
|
- [Targets (product entities)](/docs/alerts/new-relic-alerts-beta/configuring-alert-policies/select-product-targets-alert-condition) per condition
+ [Targets (product entities)](/docs/new-relic-solutions/get-started/glossary/#alert-target) per condition
|
@@ -192,7 +192,7 @@ Limits and rules pertaining to New Relic :
|
|
- [Custom incident descriptions](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/alert-custom-incident-descriptions)
+ [Custom incident descriptions](/docs/alerts/create-alert/condition-details/alert-custom-incident-descriptions)
|
n/a
@@ -309,11 +309,11 @@ Limits and rules pertaining to New Relic :
- [Depends on channel](/docs/alerts/new-relic-alerts-beta/managing-notification-channels/notification-channels-controlling-where-send-alerts#channel-types)
+ [Depends on channel](/docs/alerts/get-notified/intro-notifications/#channels)
|
- [Depends on channel](/docs/alerts/new-relic-alerts-beta/managing-notification-channels/notification-channels-controlling-where-send-alerts#channel-types)
+ [Depends on channel](/docs/alerts/get-notified/intro-notifications/#channels)
|
diff --git a/src/content/docs/alerts/create-alert/condition-details/alert-custom-incident-descriptions.mdx b/src/content/docs/alerts/create-alert/condition-details/alert-custom-incident-descriptions.mdx
index 09a1decc8f4..5cec13aa735 100644
--- a/src/content/docs/alerts/create-alert/condition-details/alert-custom-incident-descriptions.mdx
+++ b/src/content/docs/alerts/create-alert/condition-details/alert-custom-incident-descriptions.mdx
@@ -10,6 +10,7 @@ redirects:
- /docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/alert-custom-violation-descriptions
- /docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/advanced-techniques/alert-custom-violation-descriptions/
- /docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/advanced-techniques/alert-custom-incident-descriptions
+ - /docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/alert-custom-incident-descriptions
freshnessValidatedDate: never
---
diff --git a/src/content/docs/alerts/create-alert/create-alert-condition/alert-conditions.mdx b/src/content/docs/alerts/create-alert/create-alert-condition/alert-conditions.mdx
index 8284b0bcc9a..b1534c75723 100644
--- a/src/content/docs/alerts/create-alert/create-alert-condition/alert-conditions.mdx
+++ b/src/content/docs/alerts/create-alert/create-alert-condition/alert-conditions.mdx
@@ -15,6 +15,7 @@ redirects:
- /docs/alerts/create-alert/create-alert-condition/update-or-disable-policies-conditions
- /docs/alerts/new-relic-alerts-beta/configuring-alert-policies/define-alert-conditions
- /docs/alerts/new-relic-alerts/configuring-alert-policies/define-alert-conditions
+ - /docs/alerts/new-relic-alerts-beta/configuring-alert-policies/select-product-targets-alert-condition
freshnessValidatedDate: never
---
diff --git a/src/content/docs/alerts/create-alert/examples/define-custom-metrics-alert-condition.mdx b/src/content/docs/alerts/create-alert/examples/define-custom-metrics-alert-condition.mdx
index 8e999a90580..04c43bdfba5 100644
--- a/src/content/docs/alerts/create-alert/examples/define-custom-metrics-alert-condition.mdx
+++ b/src/content/docs/alerts/create-alert/examples/define-custom-metrics-alert-condition.mdx
@@ -25,7 +25,7 @@ To alert on custom metrics, follow standard procedures to [add a condition](/doc
Use the policy's **Thresholds** section to define the custom metric values. These include:
-* The custom metric name for the selected product category and [targets](/docs/alerts/new-relic-alerts-beta/configuring-alert-policies/select-product-targets-alert-condition).
+* The custom metric name for the selected product category and [targets](/docs/new-relic-solutions/get-started/glossary/#alert-target).
* Selected threshold value function of either average, minimum, maximum, total value per minute, or throughput.
* Selected threshold level of either above, below, or equal to.
* Critical and warning threshold value and duration that will open an incident, such as `5 units for at least 5 minutes`.
@@ -45,7 +45,7 @@ To define the custom metric values for your condition:
2. Click on the policy you'd like to create the classic alert condition, or create a new policy.
3. Select **New alert condition**, then select **Build a classic alert**.
4. From the **Categorize** section, select the [product and type of condition](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/create-alert-conditions) for the custom metric.
-5. From the **Select entities** section, add one or more [targets (entities)](/docs/alerts/new-relic-alerts-beta/configuring-alert-policies/select-product-targets-alert-condition) that use your custom metric.
+5. From the **Select entities** section, add one or more [targets (entities)](/docs/new-relic-solutions/get-started/glossary/#alert-target) that use your custom metric.
6. From the **Set thresholds** section, select one of the metrics from the **Custom Metrics** section in the Select drop down.
7. Provide the [required threshold values](#custom-metrics-requirements) for your custom metric.
diff --git a/src/content/docs/alerts/get-notified/intro-notifications.mdx b/src/content/docs/alerts/get-notified/intro-notifications.mdx
index 59ee20a42ea..af79b136c91 100644
--- a/src/content/docs/alerts/get-notified/intro-notifications.mdx
+++ b/src/content/docs/alerts/get-notified/intro-notifications.mdx
@@ -9,6 +9,7 @@ metaDescription: "Notifications are how you integrate your New Relic data with t
freshnessValidatedDate: never
redirects:
- /docs/alerts-applied-intelligence/notifications/intro-notifications
+ - /docs/alerts/new-relic-alerts-beta/managing-notification-channels/notification-channels-controlling-where-send-alerts
---
DevOps teams have a lot to monitor as systems grow increasingly complex and it can be hard to keep track of what is going on, where. Notifications is a suite of tools that enable you to get the right information to the right people as soon as possible. Notifications send notification events to third-party services, such as Slack, Jira, ServiceNow, and email. You can also use webhooks to send your data to any compatible third-party service.
diff --git a/src/content/docs/apm/agents/net-agent/net-agent-api/net-agent-api.mdx b/src/content/docs/apm/agents/net-agent/net-agent-api/net-agent-api.mdx
index 16c7db3900a..53100001667 100644
--- a/src/content/docs/apm/agents/net-agent/net-agent-api/net-agent-api.mdx
+++ b/src/content/docs/apm/agents/net-agent/net-agent-api/net-agent-api.mdx
@@ -287,7 +287,7 @@ The following list contains the different calls you can make with the API, inclu
```aspnet
@@ -312,7 +312,7 @@ The following list contains the different calls you can make with the API, inclu
```cshtml
@@ -339,7 +339,7 @@ The following list contains the different calls you can make with the API, inclu
@@ -595,7 +595,7 @@ The following list contains the different calls you can make with the API, inclu
@@ -839,7 +839,7 @@ The following list contains the different calls you can make with the API, inclu
@@ -873,7 +873,7 @@ The following list contains the different calls you can make with the API, inclu
### Syntax
@@ -1046,7 +1046,7 @@ The following list contains the different calls you can make with the API, inclu
Provides access to the currently executing [span](/docs/apm/agents/net-agent/net-agent-api/net-agent-api/#ISpan), making span-specific methods available within the New Relic API.
@@ -1061,7 +1061,7 @@ The following list contains the different calls you can make with the API, inclu
### Syntax
@@ -1115,7 +1115,7 @@ The following list contains the different calls you can make with the API, inclu
```
### Syntax
@@ -1302,7 +1302,7 @@ The following list contains the different calls you can make with the API, inclu
Adds contextual information about your application to the current span in the form of [attributes](/docs/using-new-relic/welcome-new-relic/get-started/glossary#attribute).
@@ -1477,7 +1477,7 @@ The following list contains the different calls you can make with the API, inclu
Changes the name of the current segment/span that will be reported to New Relic. For segments/spans resulting from custom instrumentation, the metric name reported to New Relic will be altered as well.
@@ -1697,7 +1697,7 @@ The following list contains the different calls you can make with the API, inclu
```cs
@@ -1734,7 +1734,7 @@ The following list contains the different calls you can make with the API, inclu
```cs
@@ -1783,7 +1783,7 @@ The following list contains the different calls you can make with the API, inclu
```cs
@@ -1833,7 +1833,7 @@ The following list contains the different calls you can make with the API, inclu
```cs
diff --git a/src/content/docs/apm/agents/nodejs-agent/getting-started/monitor-your-nodejs-app.mdx b/src/content/docs/apm/agents/nodejs-agent/getting-started/monitor-your-nodejs-app.mdx
index c0ce343cc3c..573ca88ff2e 100644
--- a/src/content/docs/apm/agents/nodejs-agent/getting-started/monitor-your-nodejs-app.mdx
+++ b/src/content/docs/apm/agents/nodejs-agent/getting-started/monitor-your-nodejs-app.mdx
@@ -15,7 +15,7 @@ Want to learn more before you get started? [Introduction to APM](/docs/apm/new-r
## What do you want to monitor? [#what]
- Is your application running on a Kubernetes cluster? Try out our installation method using the [Kubernetes agents operator](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator/).
+ Is your application running on a Kubernetes cluster? Try out our installation method using the [Kubernetes APM auto-attach](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator/).
We have a few paths to install the Node.js agent, depending on what you're monitoring.
diff --git a/src/content/docs/apm/agents/python-agent/configuration/python-agent-configuration.mdx b/src/content/docs/apm/agents/python-agent/configuration/python-agent-configuration.mdx
index 21c04d7d77a..3bfdd0e38b0 100644
--- a/src/content/docs/apm/agents/python-agent/configuration/python-agent-configuration.mdx
+++ b/src/content/docs/apm/agents/python-agent/configuration/python-agent-configuration.mdx
@@ -5372,7 +5372,7 @@ Here are assorted other settings available via the agent configuration file.
- If this setting is enabled, the agent will send detailed troubleshooting messages from its startup scripts directly to your console (STDOUT). This can be helpful for debugging crashes in the `newrelic-admin` startup script, the alternative `bootstrap/sitecustomize.py` startup script, or the startup sequence of the Kubernetes Agents Operator.
+ If this setting is enabled, the agent will send detailed troubleshooting messages from its startup scripts directly to your console (STDOUT). This can be helpful for debugging crashes in the `newrelic-admin` startup script, the alternative `bootstrap/sitecustomize.py` startup script, or the startup sequence of the Kubernetes APM auto-attach.
This environment variable setting has no corresponding config file setting, as the code related to it runs before the config file is read. For comprehensive debug logging after the agent has started, set [log level](#log_level) to `debug`.
diff --git a/src/content/docs/apm/agents/ruby-agent/installation/install-new-relic-ruby-agent.mdx b/src/content/docs/apm/agents/ruby-agent/installation/install-new-relic-ruby-agent.mdx
index 135b997b372..d19b68e47a5 100644
--- a/src/content/docs/apm/agents/ruby-agent/installation/install-new-relic-ruby-agent.mdx
+++ b/src/content/docs/apm/agents/ruby-agent/installation/install-new-relic-ruby-agent.mdx
@@ -29,7 +29,7 @@ Our Ruby agent auto-instruments your code so you can start monitoring applicatio
- Is your application running on a Kubernetes cluster? Try out our installation method using the [Kubernetes agents operator](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator/).
+ Is your application running on a Kubernetes cluster? Try out our installation method using the [Kubernetes APM auto-attach](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator/).
## Install the gem [#Installing_the_Gem]
diff --git a/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator.mdx b/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator.mdx
index 9b783761c4e..b02efc383e9 100644
--- a/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator.mdx
+++ b/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator.mdx
@@ -1,11 +1,11 @@
---
-title: 'Kubernetes APM Auto-attach (former agent operator)'
+title: 'Kubernetes APM auto-attach'
tags:
- Integrations
- Kubernetes integration
- Agent Operator
- - APM Auto-attach
-metaDescription: "Learn how to use the Kubernetes APM Auto-attach to automatically manage your APM agents."
+ - APM auto-attach
+metaDescription: "Learn how to use the Kubernetes APM auto-attach to automatically manage your APM agents."
freshnessValidatedDate: 2024-06-28
---
@@ -15,7 +15,7 @@ freshnessValidatedDate: 2024-06-28
This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy).
-The Kubernetes APM Auto-attach streamlines full-stack observability for Kubernetes environments by automating APM instrumentation alongside Kubernetes agent deployment. By enabling auto instrumentation, developers no longer need to manually manage [APM agents](/docs/apm/new-relic-apm/getting-started/introduction-apm/). The Kubernetes APM Auto-attach will automatically install, upgrade and remove APM agents.
+The Kubernetes APM auto-attach, formerly known as the Kubernetes agent operator, streamlines full-stack observability for Kubernetes environments by automating APM instrumentation alongside Kubernetes agent deployment. By enabling auto instrumentation, developers no longer need to manually manage [APM agents](/docs/apm/new-relic-apm/getting-started/introduction-apm/). The Kubernetes APM auto-attach will automatically install, upgrade and remove APM agents.
It currently [supports](#k8s-supported-versions) Java, .NET, Node.js, Python, and Ruby with additional languages (PHP and Go) on the way.
@@ -44,13 +44,13 @@ Before installing the operator, check the following:
## Installation [#install-k8s-operator]
-Depending on what you need, you can choose to install the Kubernetes APM Auto-attach independently or together with our K8s integrations.
+Depending on what you need, you can choose to install the Kubernetes APM auto-attach independently or together with our Kubernetes integrations.
We strongly recommend to install it together with the Kubernetes integration to take advantage of our entire [full stack observability](/docs/apm/apm-ui-pages/monitoring/kubernetes-summary-page/) experience.
### Bundle installation in addition to the Kubernetes integration (recommended) [#bundle-installation]
-The Kubernetes APM Auto-attach chart is part of the [`nri-bundle`](https://github.com/newrelic/helm-charts/tree/master/charts/nri-bundle) chart, which manages the installation of all the components needed to enable a full Kubernetes observability.
+The Kubernetes APM auto-attach chart is part of the [`nri-bundle`](https://github.com/newrelic/helm-charts/tree/master/charts/nri-bundle) chart, which manages the installation of all the components needed to enable a full Kubernetes observability.
Add the `k8s-agents-operator.enabled=true` parameter to your helm command or include it in the [`values.yaml`](https://github.com/newrelic/helm-charts/blob/master/charts/nri-bundle/values.yaml) file. See the [Install the Kubernetes integration](/install/kubernetes/?dropdown1=helm) page for more information about using Helm or check out the [`nri-bundle`](https://github.com/newrelic/helm-charts/tree/master/charts/nri-bundle) chart.
@@ -73,7 +73,7 @@ helm upgrade --install newrelic-bundle newrelic/nri-bundle \
### Standalone installation [#standalone-installation]
-To install the Kubernetes APM Auto-attach with the default configuration, run these commands:
+To install the Kubernetes APM auto-attach with the default configuration, run these commands:
```shell
helm repo add k8s-agents-operator https://newrelic.github.io/k8s-agents-operator
@@ -87,7 +87,7 @@ For a complete list of configuration options, see the [README](https://github.co
## Configure auto-instrumentation [#configure-auto-instrumentation]
-After APM Auto-attach is all set up in your cluster, the next step is just to roll out the configs required to get it operational. That involves having at least one instrumentation Custom Resource (CR) active in the cluster.
+After APM auto-attach is all set up in your cluster, the next step is just to roll out the configs required to get it operational. That involves having at least one instrumentation Custom Resource (CR) active in the cluster.
Here's what the instrumentation CR lets you map out:
@@ -390,7 +390,7 @@ When you install it, a is created and it's th
## Update APM instrumentation in applications [#upgrade-apm-instrumention]
-By default, the Kubernetes APM Auto-attach automatically installs the latest available version of the corresponding [APM agent](/docs/apm/new-relic-apm/getting-started/introduction-apm/).
+By default, the Kubernetes APM auto-attach automatically installs the latest available version of the corresponding [APM agent](/docs/apm/new-relic-apm/getting-started/introduction-apm/).
Once the monitoring of an application starts, it's not automatically updated to a newer version unless you choose to update. You can update the application by redeploying the pods or restarting your deployment.
@@ -398,7 +398,7 @@ Once the monitoring of an application starts, it's not automatically updated to
To remove the APM instrumentation from an application, you must change the matching label selector inside either the `podLabelSelector` or `namespaceLabelSelector` used or delete the instrumentation CR. Then, restart the deployment. The remove process takes just a few seconds.
-## Update the Kubernetes APM Auto-attach [#update-k8s-auto-attach]
+## Update the Kubernetes APM auto-attach [#update-k8s-auto-attach]
### Bundle installation [#upgrading-bundle-installation]
@@ -410,17 +410,17 @@ k8s-agents-operator.enabled=true
### Standalone installation [#standalone-installation]
-Run the `helm upgrade` command to update to a newer version of the Kubernetes APM Auto-attach.
+Run the `helm upgrade` command to update to a newer version of the Kubernetes APM auto-attach.
```shell
helm upgrade k8s-agents-operator newrelic/k8s-agents-operator -n newrelic
```
-## Uninstalling the Kubernetes APM Auto-attach [#uninstall-k8s-auto-attach]
+## Uninstalling the Kubernetes APM auto-attach [#uninstall-k8s-auto-attach]
### Bundle installation [#uninstall-bundle-installation]
-Uninstall the `nri-bundle` chart or if you only want to remove Kubernetes APM Auto-attach, run a helm upgrade with the following parameter:
+Uninstall the `nri-bundle` chart or if you only want to remove Kubernetes APM auto-attach, run a helm upgrade with the following parameter:
```shell
k8s-agents-operator.enabled=false
@@ -428,7 +428,7 @@ k8s-agents-operator.enabled=false
### Standalone installation [#uninstall-standalone-installation]
-To uninstall and delete the Kubernetes APM Auto-attach, run this command:
+To uninstall and delete the Kubernetes APM auto-attach, run this command:
```shell
helm uninstall k8s-agents-operator -n newrelic
@@ -442,7 +442,7 @@ helm uninstall k8s-agents-operator -n newrelic
## Certificates [#certificates]
-The K8s APM Auto-attach can support [`cert-manager`](https://github.com/cert-manager/cert-manager) if preferred.
+The Kubernetes APM auto-attach can support [`cert-manager`](https://github.com/cert-manager/cert-manager) if preferred.
* Run this command to install the [`cert-manager`](https://github.com/cert-manager/cert-manager) Helm chart:
@@ -473,13 +473,13 @@ Run this command to see the available charts:
Yes, you just need to add more secrets in the cluster. Check needed steps in the [license keys (optional)](#license-keys]) section.
- The [K8s APM experience](/docs/apm/apm-ui-pages/monitoring/kubernetes-summary-page/) is only available on the account where the data from the applications and the K8s cluster is available.
+ The [K8s APM experience](/docs/apm/apm-ui-pages/monitoring/kubernetes-summary-page/) is only available on the account where the data from the applications and the Kubernetes cluster is available.
Installing two APM agents in the same application can potentially lead to unexpected issues. Therefore, we strongly recommend removing any existing instrumentation before installing it.
@@ -487,7 +487,7 @@ Run this command to see the available charts:
Yes, custom instrumentation will work the same as without APM auto-attach. The main difference is that the agent is now injected by APM auto-attach instead of installed in the container with the rest of the application dependencies.
@@ -502,7 +502,7 @@ Run this command to see the available charts:
No, you can't. The APM agents are injected at application runtime, it needs access to write to the application container's file system.
@@ -511,7 +511,7 @@ Run this command to see the available charts:
It only supports Linux nodes.
@@ -521,7 +521,7 @@ Run this command to see the available charts:
It hasn't been tested on [AWS Fargate](/docs/kubernetes-pixie/kubernetes-integration/installation/kubernetes-eks-fargate/) nodes with EKS.
@@ -532,7 +532,7 @@ Run this command to see the available charts:
If your applications are not instrumented, you should check the following:
-* Please be sure to redeploy or deploy new applications after you've installed K8s APM auto-attach. Notice that only auto-instruments new applications are deployed in the cluster.
+* Please be sure to redeploy or deploy new applications after you've installed Kubernetes APM auto-attach. Notice that only auto-instruments new applications are deployed in the cluster.
* Run this command to check that the secret is installed in the app's namespace:
@@ -566,7 +566,7 @@ It's advised to uninstall any versions preceding 0.14 and proceed with the insta
## Support [#support]
-The Kubernetes APM Auto-attach currently supports the latest version of these APM agents: Java, .NET, Node.js, Python, and Ruby.
+The Kubernetes APM auto-attach currently supports the latest version of these APM agents: Java, .NET, Node.js, Python, and Ruby.
Once is on general availability, the latest 3 versions of each of the APM agents will be supported.
diff --git a/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-otel.mdx b/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-otel.mdx
index 064b60c3d39..05a4eebd7b3 100644
--- a/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-otel.mdx
+++ b/src/content/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-otel.mdx
@@ -13,7 +13,7 @@ freshnessValidatedDate: 2024-07-23
This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy).
-OpenTelemetry observability for Kubernetes provides complete, open-source setup paired with a top-notch Kubernetes UI that is already compatible with our proprietary Kubernetes instrumentation. Our K8s UIs are designed to be provider agnostic, allowing you to select either OpenTelemetry or New Relic instrumentation based on your needs.
+OpenTelemetry observability for Kubernetes provides complete, open-source setup paired with a top-notch Kubernetes UI that is already compatible with our proprietary Kubernetes instrumentation. Our Kubernetes UIs are designed to be provider agnostic, allowing you to select either OpenTelemetry or New Relic instrumentation based on your needs.
This document outlines the process for monitoring a Kubernetes cluster using OpenTelemetry. It involves the installation of the [`nr-k8s-otel-collector`](https://github.com/newrelic/helm-charts/tree/master/charts/nr-k8s-otel-collector) Helm chart within the cluster and the deployment of the necessary Collectors to enable first-class observability.
diff --git a/src/content/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/record-handled-exceptions.mdx b/src/content/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/record-handled-exceptions.mdx
index e9a9d16441e..5a8d55fb0a7 100644
--- a/src/content/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/record-handled-exceptions.mdx
+++ b/src/content/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/record-handled-exceptions.mdx
@@ -41,9 +41,9 @@ freshnessValidatedDate: 2023-07-20
- ## Syntax [#syntax]
+ ## Syntax [#android-syntax]
- ### Java [#java]
+ ### Java [#android-syntax-java]
```java
NewRelic.recordHandledException(Exception $exceptionToHandle)
@@ -55,7 +55,7 @@ freshnessValidatedDate: 2023-07-20
NewRelic.recordHandledException(Throwable $throwableToHandle, Map of String, Object $exceptionAttributes)
```
- ### Kotlin [#kotlin]
+ ### Kotlin [#android-syntax-kotlin]
```kotlin
NewRelic.recordHandledException(
@@ -72,7 +72,7 @@ freshnessValidatedDate: 2023-07-20
)
```
- ## Description [#description]
+ ## Description [#android-description]
Records a handled exception or other throwable type. Optionally takes map with additional attributes showing context.
@@ -80,7 +80,7 @@ freshnessValidatedDate: 2023-07-20
In addition to associated custom attributes, the events will also have associated [session attributes](/docs/insights/insights-data-sources/default-attributes/mobile-default-attributes-insights). You can view event data in the mobile monitoring UI in the [Crash event trail](/docs/mobile-monitoring/mobile-monitoring-ui/crashes/mobile-crash-event-trail), or via NRQL.
- ## Parameters [#parameters]
+ ## Parameters [#android-parameters]
@@ -130,15 +130,15 @@ freshnessValidatedDate: 2023-07-20
- ## Return values [#return-values]
+ ## Return values [#android-return-values]
Returns `true` if recorded successfully, or `false` if not.
- ## Examples [#examples]
+ ## Examples [#android-examples]
Here's an example of recording a `ClassCastException` from within an on-click listener:
- ### Java [#java]
+ ### Java [#android-examples-java]
```java
public class MainActivity extends Activity {
@@ -159,7 +159,7 @@ freshnessValidatedDate: 2023-07-20
}
```
- ### Kotlin [#kotlin]
+ ### Kotlin [#android-examples-kotlin]
```kotlin
@@ -182,7 +182,7 @@ freshnessValidatedDate: 2023-07-20
- ## Syntax [#syntax]
+ ## Syntax [#ios-syntax]
### Objective-c
@@ -190,7 +190,7 @@ freshnessValidatedDate: 2023-07-20
recordHandledException:(NSException* __nonnull)exception withAttributes:(NSDictionary* __nullable)attributes;
```
- ## Description [#description]
+ ## Description [#ios-description]
Records a handled exception (Objective-c only). Optionally takes a map with additional attributes showing context.
@@ -199,10 +199,10 @@ freshnessValidatedDate: 2023-07-20
This API takes an instance of an `NSException` and an optional `NSDictionary` attribute dictionary, then creates a `recordHandledException` event. You can view event data in the [Crash event trail UI](/docs/mobile-monitoring/mobile-monitoring-ui/crashes/mobile-crash-event-trail), and query them with NRQL.
- This function should not be used with Swift code. Please use [recordError](/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/record-errors/) to track handled errors in Swift code.
+ This function should not be used with Swift code. Please use [`recordError`](/docs/mobile-monitoring/new-relic-mobile/mobile-sdk/record-errors/) to track handled errors in Swift code.
- ## Parameters [#parameters]
+ ## Parameters [#ios-parameters]
@@ -252,11 +252,11 @@ freshnessValidatedDate: 2023-07-20
- ## Return values [#return-values]
+ ## Return values [#ios-return-values]
Returns `true` if the event is recorded successfully, or `false` if not.
- ## Examples [#examples]
+ ## Examples [#ios-examples]
Here's an example of a simple handled exception:
@@ -282,18 +282,18 @@ freshnessValidatedDate: 2023-07-20
```
-
- ## Syntax [#syntax]
+
+ ## Syntax [#maui-syntax]
```csharp
recordError(error, StackTrace.current, attributes: attributes);
```
- ## Description [#description]
+ ## Description [#maui-description]
Manually record non-fatal exceptions.
- ## Parameters [#parameters]
+ ## Parameters [#maui-parameters]
@@ -329,11 +329,11 @@ freshnessValidatedDate: 2023-07-20
- ## Return values [#return-values]
+ ## Return values [#maui-return-values]
Returns `true` if the event is recorded successfully, or `false` if not.
- ## Example [#example]
+ ## Example [#maui-example]
```dart
try {
@@ -345,18 +345,18 @@ freshnessValidatedDate: 2023-07-20
```
-
- ## Syntax [#syntax]
+
+ ## Syntax [#unity-syntax]
```csharp
RecordException(System.Exception exception) : void;
```
- ## Description [#description]
+ ## Description [#unity-description]
Records a handled exception. Optionally takes map with additional attributes showing context.
- ## Parameters [#parameters]
+ ## Parameters [#unity-parameters]
@@ -392,11 +392,11 @@ freshnessValidatedDate: 2023-07-20
- ## Return values [#return-values]
+ ## Return values [#unity-return-values]
Returns `true` if the event is recorded successfully, or `false` if not.
- ## Example [#example]
+ ## Example [#unity-example]
```csharp
try {
@@ -407,80 +407,18 @@ freshnessValidatedDate: 2023-07-20
```
-
- ## Syntax [#syntax]
-
-```csharp
- RecordException(System.Exception exception) : void;
-```
-
- ## Description [#description]
-
- Manually record any handled exceptions.
-
- ## Parameters [#parameters]
-
-
-
-
- |
- Parameter
- |
-
-
- Type
- |
-
-
- Description
- |
-
-
-
-
-
- |
- `exception`
- |
-
-
- `Exception`
- |
-
-
- Required. The exception to be recorded.
- |
-
-
-
-
- ## Return values [#return-values]
-
- Returns `true` if the event is recorded successfully, or `false` if not.
-
- ## Example [#example]
-
-```csharp
- try {
- some_code_that_throws_error();
- } catch (Exception ex) {
- NewRelicAgent.RecordException(e);
- }
-```
-
-
- ## Syntax [#syntax]
+ ## Syntax [#xamarin-syntax]
```csharp
RecordException(System.Exception exception) : void;
```
- ## Description [#description]
+ ## Description [#xamarin-description]
Manually record any handled exceptions.
- ## Parameters [#parameters]
+ ## Parameters [#xamarin-parameters]
@@ -516,17 +454,17 @@ freshnessValidatedDate: 2023-07-20
- ## Return values [#return-values]
+ ## Return values [#xamarin-return-values]
Returns `true` if the event is recorded successfully, or `false` if not.
- ## Example [#example]
+ ## Example [#xamarin-example]
```csharp
try {
some_code_that_throws_error();
} catch (Exception ex) {
- CrossNewRelicClient.Current.RecordException(ex);
+ NewRelicAgent.RecordException(e);
}
```
diff --git a/src/content/docs/new-relic-solutions/get-started/glossary.mdx b/src/content/docs/new-relic-solutions/get-started/glossary.mdx
index 44e32f84dd3..8d221f103e0 100644
--- a/src/content/docs/new-relic-solutions/get-started/glossary.mdx
+++ b/src/content/docs/new-relic-solutions/get-started/glossary.mdx
@@ -1117,7 +1117,7 @@ Whether you're considering New Relic or you're already using our capabilities, t
id="alert-target"
title="target"
>
- In the context of alerting, a **target** is a resource or component monitored by a New Relic monitoring tool that has been [identified in an alert condition](/docs/alerts/new-relic-alerts-beta/configuring-alert-policies/select-product-targets-alert-condition). When the data source for that target crosses the defined critical threshold, we open an incident. Depending on your policy's [incident preference](/docs/alerts/new-relic-alerts/configuring-alert-policies/specify-when-new-relic-creates-incidents) setting, alerts may create an incident record and send notifications through the defined channels. See also [**entity**](#entity).
+ In the context of alerting, a **target** is a resource or component monitored by a New Relic monitoring tool that has been identified in an [alert condition](/docs/alerts/create-alert/create-alert-condition/alert-conditions/). When the data source for that target crosses the defined critical threshold, we open an incident. Depending on your policy's [incident preference](/docs/alerts/new-relic-alerts/configuring-alert-policies/specify-when-new-relic-creates-incidents) setting, alerts may create an incident record and send notifications through the defined channels. See also [**entity**](#entity).
- Is your application running on a Kubernetes cluster? Try out our installation method using the [Kubernetes agents operator](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator/).
+ Is your application running on a Kubernetes cluster? Try out our installation method using the [Kubernetes APM auto-attach](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator/).
diff --git a/src/install/python/python-agent-intro.mdx b/src/install/python/python-agent-intro.mdx
index c7bb86944e0..f8bcf1d4da6 100644
--- a/src/install/python/python-agent-intro.mdx
+++ b/src/install/python/python-agent-intro.mdx
@@ -19,7 +19,7 @@ Use the New Relic Python agent to solve your app's performance issues with our [
## Start our interactive instructions
- Is your application running in a Kubernetes cluster? Try out our installation method using the [Kubernetes agents operator](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator/).
+ Is your application running in a Kubernetes cluster? Try out our installation method using the [Kubernetes APM auto-attach](/docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator/).
This page is interactive, which means we'll ask you some questions about your environment so we can give you specific steps to install the Python agent. Here's what we want to know:
diff --git a/src/nav/kubernetes-pixie.yml b/src/nav/kubernetes-pixie.yml
index 19a3758db55..342a9d6c906 100644
--- a/src/nav/kubernetes-pixie.yml
+++ b/src/nav/kubernetes-pixie.yml
@@ -19,7 +19,7 @@ pages:
path: /docs/kubernetes-pixie/kubernetes-integration/installation/upgrading-kubernetes
- title: Reduce data ingested
path: /docs/kubernetes-pixie/kubernetes-integration/installation/reduce-ingest
- - title: Kubernetes APM Auto-attach
+ - title: Kubernetes APM auto-attach
path: /docs/kubernetes-pixie/kubernetes-integration/installation/k8s-agent-operator
- title: Manage Kubernetes alerts
pages: