diff --git a/deploy-manage/cloud-organization/tools-and-apis.md b/deploy-manage/cloud-organization/tools-and-apis.md index c243a4e086..c295caa97e 100644 --- a/deploy-manage/cloud-organization/tools-and-apis.md +++ b/deploy-manage/cloud-organization/tools-and-apis.md @@ -34,7 +34,7 @@ Kibana APIs Other Products : Most other Elastic products have APIs to support machine-to-machine operations. You can find the documentation for these at the following links: - * [APM event intake API Reference](https://www.elastic.co/guide/en/apm/guide/current/api-events.html) + * [APM event intake API Reference](/solutions/observability/apps/elastic-apm-events-intake-api.md) * [App Search API Reference](https://www.elastic.co/guide/en/app-search/current/api-reference.html) * [Elastic Security APIs](https://www.elastic.co/guide/en/security/current/security-apis.html) * [Enterprise Search management APIs](https://www.elastic.co/guide/en/enterprise-search/current/management-apis.html) diff --git a/deploy-manage/deploy/cloud-enterprise/switch-from-apm-to-integrations-server-payload.md b/deploy-manage/deploy/cloud-enterprise/switch-from-apm-to-integrations-server-payload.md index 91addf380f..a05cc41044 100644 --- a/deploy-manage/deploy/cloud-enterprise/switch-from-apm-to-integrations-server-payload.md +++ b/deploy-manage/deploy/cloud-enterprise/switch-from-apm-to-integrations-server-payload.md @@ -12,7 +12,7 @@ This example shows how to use the Elastic Cloud Enterprise RESTful API to switch Given a deployment that is using an APM & Fleet Server with Elastic Stack version 8.0 or later, it is possible to start using Integrations Server instead by updating the deployment with an Integrations Server payload. Switching from APM & Fleet Server to Integrations Server in this way ensures that the endpoints and credentials currently used by APM Server and Fleet Server remain the same after the switch. -In order to start using the Integrations Server payload, you first need to enable the APM integration for Elastic Agent by following the steps in [Switch to the Elastic APM integration](https://www.elastic.co/guide/en/apm/guide/current/apm-integration-upgrade-steps-ess.html). +In order to start using the Integrations Server payload, you first need to enable the APM integration for Elastic Agent by following the steps in [Switch to the Elastic APM integration](/solutions/observability/apps/switch-an-elastic-cloud-cluster-to-apm-integration.md). ## API request example [ece_api_request_example_3] diff --git a/deploy-manage/deploy/cloud-on-k8s/advanced-configuration.md b/deploy-manage/deploy/cloud-on-k8s/advanced-configuration.md index 9485e32f5d..e69e1d0faa 100644 --- a/deploy-manage/deploy/cloud-on-k8s/advanced-configuration.md +++ b/deploy-manage/deploy/cloud-on-k8s/advanced-configuration.md @@ -102,7 +102,7 @@ The APM Server keystore can be used to store sensitive settings in the APM Serve password: "${ES_PASSWORD}" ``` -3. Reference the key in the APM Server configuration, as described in the [Secrets keystore for secure settings](https://www.elastic.co/guide/en/apm/server/current/keystore.html). +3. Reference the key in the APM Server configuration, as described in the [Secrets keystore for secure settings](/solutions/observability/apps/secrets-keystore-for-secure-settings.md). ## Reference an existing Elasticsearch cluster [k8s-apm-existing-es] diff --git a/deploy-manage/deploy/cloud-on-k8s/configure-eck.md b/deploy-manage/deploy/cloud-on-k8s/configure-eck.md index 18c796e469..9497496909 100644 --- a/deploy-manage/deploy/cloud-on-k8s/configure-eck.md +++ b/deploy-manage/deploy/cloud-on-k8s/configure-eck.md @@ -22,7 +22,7 @@ ECK can be configured using either command line flags or environment variables. | `disable-telemetry` | `false` | Disable periodically updating ECK telemetry data for Kibana to consume. | | `elasticsearch-client-timeout` | `180s` | Default timeout for requests made by the Elasticsearch client. | | `enable-leader-election` | `true` | Enable leader election. Must be set to true if using multiple replicas of the operator | -| `enable-tracing` | `false` | Enable APM tracing in the operator process. Use environment variables to configure APM server URL, credentials, and so on. Check [Apm Go Agent reference](https://www.elastic.co/guide/en/apm/agent/go/1.x/configuration.html) for details. | +| `enable-tracing` | `false` | Enable APM tracing in the operator process. Use environment variables to configure APM server URL, credentials, and so on. Check [Apm Go Agent reference](https://www.elastic.co/guide/en/apm/agent/go/current/configuration.html) for details. | | `enable-webhook` | `false` | Enables a validating webhook server in the operator process. | | `enforce-rbac-on-refs` | `false` | Enables restrictions on cross-namespace resource association through RBAC. | | `exposed-node-labels` | `""` | List of Kubernetes node labels which are allowed to be copied as annotations on the Elasticsearch Pods. Check [Topology spread constraints and availability zone awareness](advanced-elasticsearch-node-scheduling.md#k8s-availability-zone-awareness) for more details. | diff --git a/deploy-manage/deploy/cloud-on-k8s/connect-to-apm-server.md b/deploy-manage/deploy/cloud-on-k8s/connect-to-apm-server.md index a67608d3e2..1eb744a0be 100644 --- a/deploy-manage/deploy/cloud-on-k8s/connect-to-apm-server.md +++ b/deploy-manage/deploy/cloud-on-k8s/connect-to-apm-server.md @@ -42,6 +42,6 @@ For more information, check [APM Server Reference](https://www.elastic.co/guide/ ## APM Server API keys [k8s-apm-api-keys] -If you want to configure API keys to authorize requests to the APM Server, instead of using the APM Server CLI, you have to create API keys using the Elasticsearch [create API key API](https://www.elastic.co/guide/en/elasticsearch/reference/7.14/security-api-create-api-key.html), check the [APM Server documentation](https://www.elastic.co/guide/en/apm/server/current/api-key.html#create-api-key-workflow-es). +If you want to configure API keys to authorize requests to the APM Server, instead of using the APM Server CLI, you have to create API keys using the Elasticsearch [create API key API](https://www.elastic.co/guide/en/elasticsearch/reference/7.14/security-api-create-api-key.html), check the [APM Server documentation](/solutions/observability/apps/api-keys.md). diff --git a/deploy-manage/deploy/cloud-on-k8s/use-an-elasticsearch-cluster-managed-by-eck.md b/deploy-manage/deploy/cloud-on-k8s/use-an-elasticsearch-cluster-managed-by-eck.md index 5e58ab05ec..a4a93e0aa7 100644 --- a/deploy-manage/deploy/cloud-on-k8s/use-an-elasticsearch-cluster-managed-by-eck.md +++ b/deploy-manage/deploy/cloud-on-k8s/use-an-elasticsearch-cluster-managed-by-eck.md @@ -5,7 +5,7 @@ mapped_pages: # Use an Elasticsearch cluster managed by ECK [k8s-apm-eck-managed-es] -Managing APM Server, Kibana and Elasticsearch with ECK allows a smooth and secured integration between the stack components. The output configuration of the APM Server is setup automatically to establish a trust relationship with Elasticsearch. Specifying the Kibana reference allows ECK to automatically configure the [Kibana endpoint](https://www.elastic.co/guide/en/apm/server/current/setup-kibana-endpoint.html). +Managing APM Server, Kibana and Elasticsearch with ECK allows a smooth and secured integration between the stack components. The output configuration of the APM Server is setup automatically to establish a trust relationship with Elasticsearch. Specifying the Kibana reference allows ECK to automatically configure the [Kibana endpoint](/solutions/observability/apps/configure-kibana-endpoint.md). 1. To deploy an APM Server and connect it to the Elasticsearch cluster and Kibana instance you created in the [quickstart](deploy-an-orchestrator.md), apply the following specification: diff --git a/deploy-manage/deploy/elastic-cloud/ech-getting-started.md b/deploy-manage/deploy/elastic-cloud/ech-getting-started.md index 919f591991..5bd8b2081f 100644 --- a/deploy-manage/deploy/elastic-cloud/ech-getting-started.md +++ b/deploy-manage/deploy/elastic-cloud/ech-getting-started.md @@ -9,7 +9,7 @@ This documentation applies to Heroku users who want to make use of the Elasticse The add-on runs on the Elasticsearch Service and provides access to [Elasticsearch](https://www.elastic.co/products/elasticsearch), the open source, distributed, RESTful search engine. Many other features of the Elastic Stack are also readily available to Heroku users through the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body) after you install the add-on. For example, you can use Kibana to visualize your Elasticsearch data. -[Elasticsearch Machine Learning](https://www.elastic.co/guide/en/machine-learning/current/index.html), [Elastic Enterprise Search](https://www.elastic.co/guide/en/enterprise-search/current/index.html), [Elastic APM](https://www.elastic.co/guide/en/apm/guide/8.4/apm-overview.html) and [Elastic Fleet Server](https://www.elastic.co/guide/en/fleet/current/fleet-overview.html) are not supported by the Elasticsearch Add-On for Heroku. +[Elasticsearch Machine Learning](https://www.elastic.co/guide/en/machine-learning/current/index.html), [Elastic Enterprise Search](https://www.elastic.co/guide/en/enterprise-search/current/index.html), [Elastic APM](/solutions/observability/apps/application-performance-monitoring-apm.md) and [Elastic Fleet Server](https://www.elastic.co/guide/en/fleet/current/fleet-overview.html) are not supported by the Elasticsearch Add-On for Heroku. To learn more about what plans are available for Heroku users and their cost, check the [Elasticsearch add-on](https://elements.heroku.com/addons/foundelasticsearch) in the Elements Marketplace. diff --git a/deploy-manage/deploy/elastic-cloud/manage-integrations-server.md b/deploy-manage/deploy/elastic-cloud/manage-integrations-server.md index 4082a12089..7fde6a5748 100644 --- a/deploy-manage/deploy/elastic-cloud/manage-integrations-server.md +++ b/deploy-manage/deploy/elastic-cloud/manage-integrations-server.md @@ -5,7 +5,7 @@ mapped_pages: # Manage your Integrations server [ec-manage-integrations-server] -For deployments that are version 8.0 and later, you have the option to add a combined [Application Performance Monitoring (APM) Server](https://www.elastic.co/guide/en/apm/guide/current/apm-overview.html) and [Fleet Server](https://www.elastic.co/guide/en/fleet/current/fleet-overview.html) to your deployment. APM allows you to monitor software services and applications in real time, turning that data into documents stored in the Elasticsearch cluster. Fleet allows you to centrally manage Elastic Agents on many hosts. +For deployments that are version 8.0 and later, you have the option to add a combined [Application Performance Monitoring (APM) Server](/solutions/observability/apps/application-performance-monitoring-apm.md) and [Fleet Server](https://www.elastic.co/guide/en/fleet/current/fleet-overview.html) to your deployment. APM allows you to monitor software services and applications in real time, turning that data into documents stored in the Elasticsearch cluster. Fleet allows you to centrally manage Elastic Agents on many hosts. As part of provisioning, the APM Server and Fleet Server are already configured to work with Elasticsearch and Kibana. At the end of provisioning, you are shown the secret token to configure communication between the APM Server and the backend [APM Agents](https://www.elastic.co/guide/en/apm/agent/index.html). The APM Agents get deployed within your services and applications. @@ -20,7 +20,7 @@ From the deployment **Integrations Server** page you can also: * Fully remove the Integrations Server, delete it from the disk, and stop the charges. ::::{important} -The APM secret token can no longer be reset from the Elasticsearch Service UI. Check [Secret token](https://www.elastic.co/guide/en/apm/guide/current/secret-token.html) for instructions on managing a secret token. Note that resetting the token disrupts your APM service and restarts the server. When the server restarts, you’ll need to update all of your agents with the new token. +The APM secret token can no longer be reset from the Elasticsearch Service UI. Check [Secret token](/solutions/observability/apps/secret-token.md) for instructions on managing a secret token. Note that resetting the token disrupts your APM service and restarts the server. When the server restarts, you’ll need to update all of your agents with the new token. :::: diff --git a/deploy-manage/deploy/elastic-cloud/switch-from-apm-to-integrations-server-payload.md b/deploy-manage/deploy/elastic-cloud/switch-from-apm-to-integrations-server-payload.md index 47005dcd3b..04ff45f431 100644 --- a/deploy-manage/deploy/elastic-cloud/switch-from-apm-to-integrations-server-payload.md +++ b/deploy-manage/deploy/elastic-cloud/switch-from-apm-to-integrations-server-payload.md @@ -12,7 +12,7 @@ This example shows how to use the Elasticsearch Service RESTful API to switch fr Given a deployment that is using an APM & Fleet Server with Elastic Stack version 8.0 or later, it is possible to start using Integrations Server instead by updating the deployment with an Integrations Server payload. Switching from APM & Fleet Server to Integrations Server in this way ensures that the endpoints and credentials currently used by APM Server and Fleet Server remain the same after the switch. -In order to start using the Integrations Server payload, you first need to enable the APM integration for Elastic Agent by following the steps in [Switch to the Elastic APM integration](https://www.elastic.co/guide/en/apm/guide/current/apm-integration-upgrade-steps-ess.html). +In order to start using the Integrations Server payload, you first need to enable the APM integration for Elastic Agent by following the steps in [Switch to the Elastic APM integration](/solutions/observability/apps/switch-an-elastic-cloud-cluster-to-apm-integration.md). ### API request example [ec_api_request_example_3] @@ -376,7 +376,7 @@ Beginning with Elastic Stack version 8.0, [Integrations Server](manage-integrati :::: -You have the option to add a combined [Application Performance Monitoring (APM) Server](https://www.elastic.co/guide/en/apm/guide/current/apm-overview.html) and [Fleet Server](https://www.elastic.co/guide/en/fleet/current/fleet-overview.html) to your deployment. APM allows you to monitor software services and applications in real time, turning that data into documents stored in the Elasticsearch cluster. Fleet allows you to centrally manage Elastic Agents on many hosts. +You have the option to add a combined [Application Performance Monitoring (APM) Server](/solutions/observability/apps/application-performance-monitoring-apm.md) and [Fleet Server](https://www.elastic.co/guide/en/fleet/current/fleet-overview.html) to your deployment. APM allows you to monitor software services and applications in real time, turning that data into documents stored in the Elasticsearch cluster. Fleet allows you to centrally manage Elastic Agents on many hosts. As part of provisioning, the APM Server and Fleet Server are already configured to work with Elasticsearch and Kibana. At the end of provisioning, you are shown the secret token to configure communication between the APM Server and the backend [APM Agents](https://www.elastic.co/guide/en/apm/agent/index.html). The APM Agents get deployed within your services and applications. diff --git a/deploy-manage/users-roles/cluster-or-deployment-auth/quickstart.md b/deploy-manage/users-roles/cluster-or-deployment-auth/quickstart.md index e17ef6aced..d55b311605 100644 --- a/deploy-manage/users-roles/cluster-or-deployment-auth/quickstart.md +++ b/deploy-manage/users-roles/cluster-or-deployment-auth/quickstart.md @@ -16,7 +16,7 @@ This guide introduces you to three of {{kib}}'s security features: spaces, roles Do you have multiple teams using {{kib}}? Do you want a “playground” to experiment with new visualizations or rules? If so, then [{{kib}} Spaces](../../manage-spaces.md) can help. -Think of a space as another instance of {{kib}}. A space allows you to organize your [dashboards](../../../explore-analyze/dashboards.md), [rules](../../../explore-analyze/alerts-cases/alerts.md), [machine learning jobs](../../../explore-analyze/machine-learning/machine-learning-in-kibana.md), and much more into their own categories. For example, you might have a Marketing space for your marketeers to track the results of their campaigns, and an Engineering space for your developers to [monitor application performance](https://www.elastic.co/guide/en/apm/guide/current/apm-overview.html). +Think of a space as another instance of {{kib}}. A space allows you to organize your [dashboards](../../../explore-analyze/dashboards.md), [rules](../../../explore-analyze/alerts-cases/alerts.md), [machine learning jobs](../../../explore-analyze/machine-learning/machine-learning-in-kibana.md), and much more into their own categories. For example, you might have a Marketing space for your marketeers to track the results of their campaigns, and an Engineering space for your developers to [monitor application performance](/solutions/observability/apps/application-performance-monitoring-apm.md). The assets you create in one space are isolated from other spaces, so when you enter a space, you only see the assets that belong to that space. diff --git a/get-started/stack-components.md b/get-started/stack-components.md index b035c0fb3d..396ca57a30 100644 --- a/get-started/stack-components.md +++ b/get-started/stack-components.md @@ -27,7 +27,7 @@ $$$stack-components-agent$$$ $$$stack-components-apm$$$ APM -: Elastic APM is an application performance monitoring system built on the {{stack}}. It allows you to monitor software services and applications in real-time, by collecting detailed performance information on response time for incoming requests, database queries, calls to caches, external HTTP requests, and more. This makes it easy to pinpoint and fix performance problems quickly. [Learn more about APM](https://www.elastic.co/guide/en/apm/guide/current/apm-overview.html). +: Elastic APM is an application performance monitoring system built on the {{stack}}. It allows you to monitor software services and applications in real-time, by collecting detailed performance information on response time for incoming requests, database queries, calls to caches, external HTTP requests, and more. This makes it easy to pinpoint and fix performance problems quickly. [Learn more about APM](/solutions/observability/apps/application-performance-monitoring-apm.md). $$$stack-components-beats$$$ diff --git a/manage-data/ingest/tools.md b/manage-data/ingest/tools.md index fe82b7d985..a5477ee44f 100644 --- a/manage-data/ingest/tools.md +++ b/manage-data/ingest/tools.md @@ -19,7 +19,7 @@ mapped_urls: % Use migrated content from existing pages that map to this page: % - [ ] ./raw-migrated-files/cloud/cloud/ec-cloud-ingest-data.md -% Notes: These are resources to pull from, but this new "Ingest tools overiew" page will not be a replacement for any of these old AsciiDoc pages. File upload: https://www.elastic.co/guide/en/kibana/current/connect-to-elasticsearch.html#upload-data-kibana https://www.elastic.co/guide/en/serverless/current/elasticsearch-ingest-data-file-upload.html API: https://www.elastic.co/guide/en/kibana/current/connect-to-elasticsearch.html#_add_data_with_programming_languages https://www.elastic.co/guide/en/elasticsearch/reference/current/docs.html https://www.elastic.co/guide/en/serverless/current/elasticsearch-ingest-data-through-api.html OpenTelemetry: https://github.com/elastic/opentelemetry Fleet and Agent: https://www.elastic.co/guide/en/fleet/current/fleet-overview.html https://www.elastic.co/guide/en/serverless/current/fleet-and-elastic-agent.html Logstash: https://www.elastic.co/guide/en/logstash/current/introduction.html https://www.elastic.co/guide/en/serverless/current/elasticsearch-ingest-data-through-logstash.html https://www.elastic.co/guide/en/serverless/current/logstash-pipelines.html Beats: https://www.elastic.co/guide/en/beats/libbeat/current/beats-reference.html https://www.elastic.co/guide/en/serverless/current/elasticsearch-ingest-data-through-beats.html APM: https://www.elastic.co/guide/en/observability/current/apm.html Application logging: https://www.elastic.co/guide/en/observability/current/application-logs.html ECS logging: https://www.elastic.co/guide/en/observability/current/logs-ecs-application.html Elastic serverless forwarder for AWS: https://www.elastic.co/guide/en/esf/current/aws-elastic-serverless-forwarder.html Integrations: https://www.elastic.co/guide/en/integrations/current/introduction.html Search connectors: https://www.elastic.co/guide/en/elasticsearch/reference/current/es-connectors.html https://www.elastic.co/guide/en/serverless/current/elasticsearch-ingest-data-through-integrations-connector-client.html Web crawler: https://github.com/elastic/crawler/tree/main/docs +% Notes: These are resources to pull from, but this new "Ingest tools overiew" page will not be a replacement for any of these old AsciiDoc pages. File upload: https://www.elastic.co/guide/en/kibana/current/connect-to-elasticsearch.html#upload-data-kibana https://www.elastic.co/guide/en/serverless/current/elasticsearch-ingest-data-file-upload.html API: https://www.elastic.co/guide/en/kibana/current/connect-to-elasticsearch.html#_add_data_with_programming_languages https://www.elastic.co/guide/en/elasticsearch/reference/current/docs.html https://www.elastic.co/guide/en/serverless/current/elasticsearch-ingest-data-through-api.html OpenTelemetry: https://github.com/elastic/opentelemetry Fleet and Agent: https://www.elastic.co/guide/en/fleet/current/fleet-overview.html https://www.elastic.co/guide/en/serverless/current/fleet-and-elastic-agent.html Logstash: https://www.elastic.co/guide/en/logstash/current/introduction.html https://www.elastic.co/guide/en/serverless/current/elasticsearch-ingest-data-through-logstash.html https://www.elastic.co/guide/en/serverless/current/logstash-pipelines.html Beats: https://www.elastic.co/guide/en/beats/libbeat/current/beats-reference.html https://www.elastic.co/guide/en/serverless/current/elasticsearch-ingest-data-through-beats.html APM: /solutions/observability/apps/application-performance-monitoring-apm.md Application logging: https://www.elastic.co/guide/en/observability/current/application-logs.html ECS logging: https://www.elastic.co/guide/en/observability/current/logs-ecs-application.html Elastic serverless forwarder for AWS: https://www.elastic.co/guide/en/esf/current/aws-elastic-serverless-forwarder.html Integrations: https://www.elastic.co/guide/en/integrations/current/introduction.html Search connectors: https://www.elastic.co/guide/en/elasticsearch/reference/current/es-connectors.html https://www.elastic.co/guide/en/serverless/current/elasticsearch-ingest-data-through-integrations-connector-client.html Web crawler: https://github.com/elastic/crawler/tree/main/docs % - [ ] ./raw-migrated-files/ingest-docs/fleet/beats-agent-comparison.md % - [ ] ./raw-migrated-files/kibana/kibana/connect-to-elasticsearch.md % - [ ] https://www.elastic.co/customer-success/data-ingestion diff --git a/raw-migrated-files/cloud/cloud-enterprise/ece-manage-apm-settings.md b/raw-migrated-files/cloud/cloud-enterprise/ece-manage-apm-settings.md index b5fcd32927..b0a6a2b004 100644 --- a/raw-migrated-files/cloud/cloud-enterprise/ece-manage-apm-settings.md +++ b/raw-migrated-files/cloud/cloud-enterprise/ece-manage-apm-settings.md @@ -6,7 +6,7 @@ Starting in {{stack}} version 8.0, how you change APM settings and the settings : New deployments created in {{stack}} version 8.0 and later will be managed by {{fleet}}. * This mode requires SSL/TLS configuration. Check [TLS configuration for {{fleet}}-managed mode](../../../deploy-manage/deploy/cloud-enterprise/edit-stack-settings.md#ece-edit-apm-fleet-tls) for details. - * Check [APM integration input settings](https://www.elastic.co/guide/en/apm/guide/current/input-apm.html) for all other Elastic APM configuration options in this mode. + * Check [APM integration input settings](/solutions/observability/apps/configure-apm-server.md) for all other Elastic APM configuration options in this mode. Standalone APM Server (legacy) @@ -15,7 +15,7 @@ Standalone APM Server (legacy) Check [Edit standalone APM settings (legacy)](../../../deploy-manage/deploy/cloud-enterprise/edit-stack-settings.md#ece-edit-apm-standalone-settings-ece)for information on how to configure Elastic APM in this mode. -To learn more about the differences between these modes, or to switch from Standalone APM Server (legacy) mode to {{fleet}}-managed, check [Switch to the Elastic APM integration](https://www.elastic.co/guide/en/apm/guide/current/upgrade-to-apm-integration.html). +To learn more about the differences between these modes, or to switch from Standalone APM Server (legacy) mode to {{fleet}}-managed, check [Switch to the Elastic APM integration](/solutions/observability/apps/switch-to-elastic-apm-integration.md). ## TLS configuration for {{fleet}}-managed mode [ece-edit-apm-fleet-tls] @@ -33,7 +33,7 @@ Pick one of the following options: Elastic Cloud Enterprise supports most of the legacy APM settings. Through a YAML editor in the console, you can append your APM Server properties to the `apm-server.yml` file. Your changes to the configuration file are read on startup. ::::{important} -Be aware that some settings could break your cluster if set incorrectly and that the syntax might change between major versions. Before upgrading, be sure to review the full list of the [latest APM settings and syntax](https://www.elastic.co/guide/en/apm/guide/current/configuring-howto-apm-server.html). +Be aware that some settings could break your cluster if set incorrectly and that the syntax might change between major versions. Before upgrading, be sure to review the full list of the [latest APM settings and syntax](/solutions/observability/apps/configure-apm-server.md). :::: diff --git a/raw-migrated-files/cloud/cloud-enterprise/ece-manage-integrations-server.md b/raw-migrated-files/cloud/cloud-enterprise/ece-manage-integrations-server.md index 754177ab88..0310ad3aa3 100644 --- a/raw-migrated-files/cloud/cloud-enterprise/ece-manage-integrations-server.md +++ b/raw-migrated-files/cloud/cloud-enterprise/ece-manage-integrations-server.md @@ -1,6 +1,6 @@ # Manage your Integrations Server [ece-manage-integrations-server] -For deployments that are version 8.0 and later, you have the option to add a combined [Application Performance Monitoring (APM) Server](https://www.elastic.co/guide/en/apm/guide/current/apm-overview.html) and [Fleet Server](https://www.elastic.co/guide/en/fleet/current/fleet-overview.html) to your deployment. APM allows you to monitor software services and applications in real time, turning that data into documents stored in the Elasticsearch cluster. Fleet allows you to centrally manage Elastic Agents on many hosts. +For deployments that are version 8.0 and later, you have the option to add a combined [Application Performance Monitoring (APM) Server](/solutions/observability/apps/application-performance-monitoring-apm.md) and [Fleet Server](https://www.elastic.co/guide/en/fleet/current/fleet-overview.html) to your deployment. APM allows you to monitor software services and applications in real time, turning that data into documents stored in the Elasticsearch cluster. Fleet allows you to centrally manage Elastic Agents on many hosts. As part of provisioning, the APM Server and Fleet Server are already configured to work with Elasticsearch and Kibana. At the end of provisioning, you are shown the secret token to configure communication between the APM Server and the backend [APM Agents](https://www.elastic.co/guide/en/apm/agent/index.html). The APM Agents get deployed within your services and applications. @@ -15,7 +15,7 @@ From the deployment **Integrations Server** page you can also: * Fully remove the Integrations Server, delete it from the disk, and stop the charges. ::::{important} -The APM secret token can no longer be reset from the Elastic Cloud Enterprise UI. Check [Secret token](https://www.elastic.co/guide/en/apm/guide/current/secret-token.html) for instructions on managing a secret token. Note that resetting the token disrupts your APM service and restarts the server. When the server restarts, you’ll need to update all of your agents with the new token. +The APM secret token can no longer be reset from the Elastic Cloud Enterprise UI. Check [Secret token](/solutions/observability/apps/secret-token.md) for instructions on managing a secret token. Note that resetting the token disrupts your APM service and restarts the server. When the server restarts, you’ll need to update all of your agents with the new token. :::: diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-getting-started.md b/raw-migrated-files/cloud/cloud-heroku/ech-getting-started.md index 0b59bb59f0..45aa133301 100644 --- a/raw-migrated-files/cloud/cloud-heroku/ech-getting-started.md +++ b/raw-migrated-files/cloud/cloud-heroku/ech-getting-started.md @@ -4,7 +4,7 @@ This documentation applies to Heroku users who want to make use of the Elasticse The add-on runs on the Elasticsearch Service and provides access to [Elasticsearch](https://www.elastic.co/products/elasticsearch), the open source, distributed, RESTful search engine. Many other features of the Elastic Stack are also readily available to Heroku users through the [Elasticsearch Add-On for Heroku console](https://cloud.elastic.co?page=docs&placement=docs-body) after you install the add-on. For example, you can use Kibana to visualize your Elasticsearch data. -[Elasticsearch Machine Learning](https://www.elastic.co/guide/en/machine-learning/current/index.html), [Elastic Enterprise Search](https://www.elastic.co/guide/en/enterprise-search/current/index.html), [Elastic APM](https://www.elastic.co/guide/en/apm/guide/8.4/apm-overview.html) and [Elastic Fleet Server](https://www.elastic.co/guide/en/fleet/current/fleet-overview.html) are not supported by the Elasticsearch Add-On for Heroku. +[Elasticsearch Machine Learning](https://www.elastic.co/guide/en/machine-learning/current/index.html), [Elastic Enterprise Search](https://www.elastic.co/guide/en/enterprise-search/current/index.html), [Elastic APM](/solutions/observability/apps/application-performance-monitoring-apm.md) and [Elastic Fleet Server](https://www.elastic.co/guide/en/fleet/current/fleet-overview.html) are not supported by the Elasticsearch Add-On for Heroku. To learn more about what plans are available for Heroku users and their cost, check the [Elasticsearch add-on](https://elements.heroku.com/addons/foundelasticsearch) in the Elements Marketplace. diff --git a/raw-migrated-files/cloud/cloud-heroku/ech-manage-apm-settings.md b/raw-migrated-files/cloud/cloud-heroku/ech-manage-apm-settings.md index 8c60608b71..ac3621048e 100644 --- a/raw-migrated-files/cloud/cloud-heroku/ech-manage-apm-settings.md +++ b/raw-migrated-files/cloud/cloud-heroku/ech-manage-apm-settings.md @@ -5,7 +5,7 @@ Change how Elastic APM runs by providing your own user settings. Starting in {{s {{fleet}}-managed APM integration : New deployments created in {{stack}} version 8.0 and later will be managed by {{fleet}}. - Check [APM configuration reference](https://www.elastic.co/guide/en/observability/current/apm-configuring-howto-apm-server.html) for information on how to configure Elastic APM in this mode. + Check [APM configuration reference](/solutions/observability/apps/configure-apm-server.md) for information on how to configure Elastic APM in this mode. Standalone APM Server (legacy) @@ -14,7 +14,7 @@ Standalone APM Server (legacy) Check [Edit standalone APM settings (legacy)](../../../deploy-manage/deploy/elastic-cloud/edit-stack-settings.md#ech-edit-apm-standalone-settings) and [Supported standalone APM settings (legacy)](../../../deploy-manage/deploy/elastic-cloud/edit-stack-settings.md#ech-apm-settings) for information on how to configure Elastic APM in this mode. -To learn more about the differences between these modes, or to switch from Standalone APM Server (legacy) mode to {{fleet}}-managed, check [Switch to the Elastic APM integration](https://www.elastic.co/guide/en/apm/guide/current/upgrade-to-apm-integration.html). +To learn more about the differences between these modes, or to switch from Standalone APM Server (legacy) mode to {{fleet}}-managed, check [Switch to the Elastic APM integration](/solutions/observability/apps/switch-to-elastic-apm-integration.md). ## Edit standalone APM settings (legacy) [ech-edit-apm-standalone-settings] @@ -43,7 +43,7 @@ If a setting is not supported by Elasticsearch Add-On for Heroku, you will get a Elasticsearch Add-On for Heroku supports the following setting when running APM in standalone mode (legacy). ::::{tip} -Some settings that could break your cluster if set incorrectly are blocklisted. The following settings are generally safe in cloud environments. For detailed information about APM settings, check the [APM documentation](https://www.elastic.co/guide/en/apm/guide/current/configuring-howto-apm-server.html). +Some settings that could break your cluster if set incorrectly are blocklisted. The following settings are generally safe in cloud environments. For detailed information about APM settings, check the [APM documentation](/solutions/observability/apps/configure-apm-server.md). :::: @@ -223,7 +223,7 @@ Allow anonymous access only for specified agents and/or services. This is primar : Specifies the maximum allowed size of an event for processing by the server, in bytes. Defaults to `307200`. `output.elasticsearch.pipelines` -: Adds an array for pipeline selector configurations that support conditionals, format string-based field access, and name mappings used to [parse data using ingest node pipelines](https://www.elastic.co/guide/en/apm/guide/current/configuring-ingest-node.html). +: Adds an array for pipeline selector configurations that support conditionals, format string-based field access, and name mappings used to [parse data using ingest node pipelines](/solutions/observability/apps/application-performance-monitoring-apm.md). `apm-server.register.ingest.pipeline.enabled` : Loads the pipeline definitions to Elasticsearch when the APM Server starts up. Defaults to `false`. diff --git a/raw-migrated-files/cloud/cloud/ec-manage-apm-settings.md b/raw-migrated-files/cloud/cloud/ec-manage-apm-settings.md index 482d9bc593..a102997d5a 100644 --- a/raw-migrated-files/cloud/cloud/ec-manage-apm-settings.md +++ b/raw-migrated-files/cloud/cloud/ec-manage-apm-settings.md @@ -5,7 +5,7 @@ Change how Elastic APM runs by providing your own user settings. Starting in {{s {{fleet}}-managed APM integration : New deployments created in {{stack}} version 8.0 and later will be managed by {{fleet}}. - Check [APM configuration reference](https://www.elastic.co/guide/en/observability/current/apm-configuring-howto-apm-server.html) for information on how to configure Elastic APM in this mode. + Check [APM configuration reference](/solutions/observability/apps/configure-apm-server.md) for information on how to configure Elastic APM in this mode. Standalone APM Server (legacy) @@ -14,7 +14,7 @@ Standalone APM Server (legacy) Check [Edit standalone APM settings (legacy)](../../../solutions/observability/apps/configure-apm-server.md#ec-edit-apm-standalone-settings) and [Supported standalone APM settings (legacy)](../../../solutions/observability/apps/configure-apm-server.md#ec-apm-settings) for information on how to configure Elastic APM in this mode. -To learn more about the differences between these modes, or to switch from Standalone APM Server (legacy) mode to {{fleet}}-managed, check [Switch to the Elastic APM integration](https://www.elastic.co/guide/en/apm/guide/current/upgrade-to-apm-integration.html). +To learn more about the differences between these modes, or to switch from Standalone APM Server (legacy) mode to {{fleet}}-managed, check [Switch to the Elastic APM integration](/solutions/observability/apps/switch-to-elastic-apm-integration.md). ## Edit standalone APM settings (legacy) [ec-edit-apm-standalone-settings] @@ -43,7 +43,7 @@ If a setting is not supported by Elasticsearch Service, you will get an error me Elasticsearch Service supports the following setting when running APM in standalone mode (legacy). ::::{tip} -Some settings that could break your cluster if set incorrectly are blocklisted. The following settings are generally safe in cloud environments. For detailed information about APM settings, check the [APM documentation](https://www.elastic.co/guide/en/apm/guide/current/configuring-howto-apm-server.html). +Some settings that could break your cluster if set incorrectly are blocklisted. The following settings are generally safe in cloud environments. For detailed information about APM settings, check the [APM documentation](/solutions/observability/apps/configure-apm-server.md). :::: @@ -223,7 +223,7 @@ Allow anonymous access only for specified agents and/or services. This is primar : Specifies the maximum allowed size of an event for processing by the server, in bytes. Defaults to `307200`. `output.elasticsearch.pipelines` -: Adds an array for pipeline selector configurations that support conditionals, format string-based field access, and name mappings used to [parse data using ingest node pipelines](https://www.elastic.co/guide/en/apm/guide/current/configuring-ingest-node.html). +: Adds an array for pipeline selector configurations that support conditionals, format string-based field access, and name mappings used to [parse data using ingest node pipelines](/solutions/observability/apps/application-performance-monitoring-apm.md). `apm-server.register.ingest.pipeline.enabled` : Loads the pipeline definitions to Elasticsearch when the APM Server starts up. Defaults to `false`. diff --git a/raw-migrated-files/docs-content/serverless/observability-apm-service-map.md b/raw-migrated-files/docs-content/serverless/observability-apm-service-map.md index c79ff6f2db..7672cac389 100644 --- a/raw-migrated-files/docs-content/serverless/observability-apm-service-map.md +++ b/raw-migrated-files/docs-content/serverless/observability-apm-service-map.md @@ -10,7 +10,7 @@ We currently surface two types of service maps: ## How do service maps work? [observability-apm-service-map-how-do-service-maps-work] -Service Maps rely on distributed traces to draw connections between services. As [distributed tracing](https://www.elastic.co/guide/en/apm/guide/current/apm-distributed-tracing.html) is enabled out-of-the-box for supported technologies, so are service maps. However, if a service isn’t instrumented, or a `traceparent` header isn’t being propagated to it, distributed tracing will not work, and the connection will not be drawn on the map. +Service Maps rely on distributed traces to draw connections between services. As [distributed tracing](/solutions/observability/apps/traces.md) is enabled out-of-the-box for supported technologies, so are service maps. However, if a service isn’t instrumented, or a `traceparent` header isn’t being propagated to it, distributed tracing will not work, and the connection will not be drawn on the map. ## Visualize your architecture [observability-apm-service-map-visualize-your-architecture] diff --git a/raw-migrated-files/docs-content/serverless/observability-apm-trace-sample-timeline.md b/raw-migrated-files/docs-content/serverless/observability-apm-trace-sample-timeline.md index a75ef14a15..daf5e2c745 100644 --- a/raw-migrated-files/docs-content/serverless/observability-apm-trace-sample-timeline.md +++ b/raw-migrated-files/docs-content/serverless/observability-apm-trace-sample-timeline.md @@ -10,7 +10,7 @@ The trace sample timeline visualization is a high-level view of what your applic View a span in detail by clicking on it in the timeline waterfall. For example, when you click on an SQL Select database query, the information displayed includes the actual SQL that was executed, how long it took, and the percentage of the trace’s total time. You also get a stack trace, which shows the SQL query in your code. Finally, APM knows which files are your code and which are just modules or libraries that you’ve installed. These library frames will be minimized by default in order to show you the most relevant stack trace. ::::{tip} -A [span](https://www.elastic.co/guide/en/apm/guide/current/data-model-spans.html) is the duration of a single event. Spans are automatically captured by APM agents, and you can also define custom spans. Each span has a type and is defined by a different color in the timeline/waterfall visualization. +A [span](/solutions/observability/apps/spans.md) is the duration of a single event. Spans are automatically captured by APM agents, and you can also define custom spans. Each span has a type and is defined by a different color in the timeline/waterfall visualization. :::: diff --git a/raw-migrated-files/docs-content/serverless/observability-correlate-application-logs.md b/raw-migrated-files/docs-content/serverless/observability-correlate-application-logs.md index 3aed5dc66e..758fb50594 100644 --- a/raw-migrated-files/docs-content/serverless/observability-correlate-application-logs.md +++ b/raw-migrated-files/docs-content/serverless/observability-correlate-application-logs.md @@ -89,6 +89,6 @@ Learn more about log correlation in the agent-specific ingestion guides: * [Go](https://www.elastic.co/guide/en/apm/agent/go/current/logs.html) * [Java](https://www.elastic.co/guide/en/apm/agent/java/current/logs.html#log-correlation-ids) * [.NET](https://www.elastic.co/guide/en/apm/agent/dotnet/current/logs.html) -* [Node.js](https://www.elastic.co/guide/en/apm/agent/nodejs/current/log-correlation.html) +* [Node.js](https://www.elastic.co/guide/en/apm/agent/nodejs/current/logs.html) * [Python](https://www.elastic.co/guide/en/apm/agent/python/current/logs.html#log-correlation-ids) * [Ruby](https://www.elastic.co/guide/en/apm/agent/ruby/current/log-correlation.html) diff --git a/raw-migrated-files/docs-content/serverless/observability-plaintext-application-logs.md b/raw-migrated-files/docs-content/serverless/observability-plaintext-application-logs.md index 96df87d66a..f6c99cb5f9 100644 --- a/raw-migrated-files/docs-content/serverless/observability-plaintext-application-logs.md +++ b/raw-migrated-files/docs-content/serverless/observability-plaintext-application-logs.md @@ -388,7 +388,7 @@ Learn about correlating plaintext logs in the agent-specific ingestion guides: * [Go](https://www.elastic.co/guide/en/apm/agent/go/current/logs.html) * [Java](https://www.elastic.co/guide/en/apm/agent/java/current/logs.html#log-correlation-ids) * [.NET](https://www.elastic.co/guide/en/apm/agent/dotnet/current/logs.html) -* [Node.js](https://www.elastic.co/guide/en/apm/agent/nodejs/current/log-correlation.html) +* [Node.js](https://www.elastic.co/guide/en/apm/agent/nodejs/current/logs.html) * [Python](https://www.elastic.co/guide/en/apm/agent/python/current/logs.html#log-correlation-ids) * [Ruby](https://www.elastic.co/guide/en/apm/agent/ruby/current/log-correlation.html) diff --git a/raw-migrated-files/docs-content/serverless/security-network-page-overview.md b/raw-migrated-files/docs-content/serverless/security-network-page-overview.md index 72c62ac650..8a28e73032 100644 --- a/raw-migrated-files/docs-content/serverless/security-network-page-overview.md +++ b/raw-migrated-files/docs-content/serverless/security-network-page-overview.md @@ -52,7 +52,7 @@ The Events table includes inline actions and several customization options. To l * **Flows**: Source and destination IP addresses and countries. * **DNS**: DNS network queries. -* **HTTP**: Received HTTP requests (HTTP requests for applications using [Elastic APM](https://www.elastic.co/guide/en/observability/current/apm.html) are monitored by default). +* **HTTP**: Received HTTP requests (HTTP requests for applications using [Elastic APM](/solutions/observability/apps/application-performance-monitoring-apm.md) are monitored by default). * **TLS**: Handshake details. * **Anomalies**: Anomalies discovered by [machine learning jobs](../../../solutions/security/advanced-entity-analytics/anomaly-detection.md). diff --git a/raw-migrated-files/elasticsearch/elasticsearch-reference/how-monitoring-works.md b/raw-migrated-files/elasticsearch/elasticsearch-reference/how-monitoring-works.md index eca7ff05a8..b17343d5c2 100644 --- a/raw-migrated-files/elasticsearch/elasticsearch-reference/how-monitoring-works.md +++ b/raw-migrated-files/elasticsearch/elasticsearch-reference/how-monitoring-works.md @@ -31,6 +31,6 @@ To learn how to collect monitoring data, refer to: * [{{packetbeat}}](https://www.elastic.co/guide/en/beats/packetbeat/current/monitoring.html) * [{{winlogbeat}}](https://www.elastic.co/guide/en/beats/winlogbeat/current/monitoring.html) -* [Monitoring APM Server](https://www.elastic.co/guide/en/apm/guide/current/monitor-apm.html) +* [Monitoring APM Server](/solutions/observability/apps/monitor-apm-server.md) * [Monitoring {{agent}}s](https://www.elastic.co/guide/en/fleet/current/monitor-elastic-agent.html) {{fleet}}-managed agents) or [Configure monitoring for standalone {{agent}}s](https://www.elastic.co/guide/en/fleet/current/elastic-agent-monitoring-configuration.html) diff --git a/raw-migrated-files/elasticsearch/elasticsearch-reference/monitoring-production.md b/raw-migrated-files/elasticsearch/elasticsearch-reference/monitoring-production.md index 4b964e862e..0f81e7e020 100644 --- a/raw-migrated-files/elasticsearch/elasticsearch-reference/monitoring-production.md +++ b/raw-migrated-files/elasticsearch/elasticsearch-reference/monitoring-production.md @@ -2,7 +2,7 @@ In production, you should send monitoring data to a separate *monitoring cluster* so that historical data is available even when the nodes you are monitoring are not. -::::{important} +::::{important} {{agent}} and {{metricbeat}} are the recommended methods for collecting and shipping monitoring data to a monitoring cluster. If you have previously configured legacy collection methods, you should migrate to using [{{agent}}](../../../deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-elastic-agent.md) or [{{metricbeat}}](../../../deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-metricbeat.md) collection. Do not use legacy collection alongside other collection methods. @@ -16,7 +16,7 @@ To store monitoring data in a separate cluster: 1. Set up the {{es}} cluster you want to use as the monitoring cluster. For example, you might set up a two host cluster with the nodes `es-mon-1` and `es-mon-2`. - ::::{important} + ::::{important} * Ideally the monitoring cluster and the production cluster run on the same {{stack}} version. However, a monitoring cluster on the latest release of 9.x also works with production clusters that use the same major version. Monitoring clusters that use 9.x also work with production clusters that use the latest release of 8.x. * There must be at least one [ingest node](../../../manage-data/ingest/transform-enrich/ingest-pipelines.md) in the monitoring cluster; it does not need to be a dedicated ingest node. @@ -40,7 +40,7 @@ To store monitoring data in a separate cluster: 2. If the {{es}} {{security-features}} are enabled on the monitoring cluster, create users that can send and retrieve monitoring data: - ::::{note} + ::::{note} If you plan to use {{kib}} to view monitoring data, username and password credentials must be valid on both the {{kib}} server and the monitoring cluster. :::: @@ -79,7 +79,7 @@ To store monitoring data in a separate cluster: * [Packetbeat](https://www.elastic.co/guide/en/beats/packetbeat/current/monitoring.html) * [Winlogbeat](https://www.elastic.co/guide/en/beats/winlogbeat/current/monitoring.html) -6. (Optional) [Configure APM Server monitoring](https://www.elastic.co/guide/en/apm/guide/current/monitor-apm.html) +6. (Optional) [Configure APM Server monitoring](/solutions/observability/apps/monitor-apm-server.md) 7. (Optional) Configure {{kib}} to collect data and send it to the monitoring cluster: * [{{agent}} collection methods](../../../deploy-manage/monitor/stack-monitoring/kibana-monitoring-elastic-agent.md) @@ -88,7 +88,7 @@ To store monitoring data in a separate cluster: 8. (Optional) Create a dedicated {{kib}} instance for monitoring, rather than using a single {{kib}} instance to access both your production cluster and monitoring cluster. - ::::{note} + ::::{note} If you log in to {{kib}} using SAML, Kerberos, PKI, OpenID Connect, or token authentication providers, a dedicated {{kib}} instance is **required**. The security tokens that are used in these contexts are cluster-specific; therefore you cannot use a single {{kib}} instance to connect to both production and monitoring clusters. :::: diff --git a/raw-migrated-files/kibana/kibana/tutorial-secure-access-to-kibana.md b/raw-migrated-files/kibana/kibana/tutorial-secure-access-to-kibana.md index aeea767c76..bf50df7be2 100644 --- a/raw-migrated-files/kibana/kibana/tutorial-secure-access-to-kibana.md +++ b/raw-migrated-files/kibana/kibana/tutorial-secure-access-to-kibana.md @@ -11,7 +11,7 @@ This guide introduces you to three of {{kib}}'s security features: spaces, roles Do you have multiple teams using {{kib}}? Do you want a “playground” to experiment with new visualizations or rules? If so, then [{{kib}} Spaces](../../../deploy-manage/manage-spaces.md) can help. -Think of a space as another instance of {{kib}}. A space allows you to organize your [dashboards](../../../explore-analyze/dashboards.md), [rules](../../../explore-analyze/alerts-cases.md), [machine learning jobs](../../../explore-analyze/machine-learning/machine-learning-in-kibana.md), and much more into their own categories. For example, you might have a Marketing space for your marketeers to track the results of their campaigns, and an Engineering space for your developers to [monitor application performance](https://www.elastic.co/guide/en/apm/guide/current/apm-overview.html). +Think of a space as another instance of {{kib}}. A space allows you to organize your [dashboards](../../../explore-analyze/dashboards.md), [rules](../../../explore-analyze/alerts-cases.md), [machine learning jobs](../../../explore-analyze/machine-learning/machine-learning-in-kibana.md), and much more into their own categories. For example, you might have a Marketing space for your marketeers to track the results of their campaigns, and an Engineering space for your developers to [monitor application performance](/solutions/observability/apps/application-performance-monitoring-apm.md). The assets you create in one space are isolated from other spaces, so when you enter a space, you only see the assets that belong to that space. diff --git a/raw-migrated-files/observability-docs/observability/apm-common-problems.md b/raw-migrated-files/observability-docs/observability/apm-common-problems.md index 2c1ba10d2a..ea2de0839f 100644 --- a/raw-migrated-files/observability-docs/observability/apm-common-problems.md +++ b/raw-migrated-files/observability-docs/observability/apm-common-problems.md @@ -188,7 +188,7 @@ https://www.elastic.co/guide/en/infrastructure/guide/current/index.html These URLs, like most, include unique names. If we named transactions based on each unique URL, we’d end up with the problem described above—a very large number of different transaction names. Instead, we should strip away the unique information and group our transactions based on common information. In this case, that means naming all blog transactions, `/blog`, and all documentation transactions, `/guide`. -If you feel like you’d be losing valuable information by following this naming convention, don’t fret! You can always add additional metadata to your transactions using [labels](https://www.elastic.co/guide/en/apm/guide/current/data-model-metadata.html#data-model-labels) (indexed) or [custom context](https://www.elastic.co/guide/en/apm/guide/current/data-model-metadata.html#data-model-custom) (non-indexed). +If you feel like you’d be losing valuable information by following this naming convention, don’t fret! You can always add additional metadata to your transactions using [labels](/solutions/observability/apps/metadata.md#apm-data-model-labels) (indexed) or [custom context](/solutions/observability/apps/metadata.md#apm-data-model-custom) (non-indexed). After ensuring you’ve correctly named your transactions, you might still see errors in the Applications UI related to transaction group limit reached: @@ -230,7 +230,7 @@ As an example, some APM agents store cookie values in `http.request.cookies`. Si **Ensure a field is searchable** There are two things you can do to if you’d like to ensure a field is searchable: -1. Index your additional data as [labels](https://www.elastic.co/guide/en/apm/guide/current/data-model-metadata.html) instead. These are dynamic by default, which means they will be indexed and become searchable and aggregatable. +1. Index your additional data as [labels](/solutions/observability/apps/metadata.md) instead. These are dynamic by default, which means they will be indexed and become searchable and aggregatable. 2. Create a custom mapping for the field. diff --git a/raw-migrated-files/observability-docs/observability/apm-errors.md b/raw-migrated-files/observability-docs/observability/apm-errors.md index eee9871b65..c08615b9d0 100644 --- a/raw-migrated-files/observability-docs/observability/apm-errors.md +++ b/raw-migrated-files/observability-docs/observability/apm-errors.md @@ -1,7 +1,7 @@ # Errors [apm-errors] ::::{tip} -[Errors](https://www.elastic.co/guide/en/apm/guide/current/data-model-errors.html) are groups of exceptions with a similar exception or log message. +[Errors](/solutions/observability/apps/errors.md) are groups of exceptions with a similar exception or log message. :::: diff --git a/raw-migrated-files/observability-docs/observability/apm-lambda.md b/raw-migrated-files/observability-docs/observability/apm-lambda.md index 972d7c85e9..65f1406725 100644 --- a/raw-migrated-files/observability-docs/observability/apm-lambda.md +++ b/raw-migrated-files/observability-docs/observability/apm-lambda.md @@ -2,7 +2,7 @@ Elastic APM provides performance and error monitoring for AWS Lambda functions. See how your Lambda functions relate to and depend on other services, and get insight into function execution and runtime behavior, like lambda duration, cold start rate, cold start duration, compute usage, memory usage, and more. -To set up Lambda monitoring, see the relevant [quick start guide](https://www.elastic.co/guide/en/apm/guide/current/monitoring-aws-lambda.html). +To set up Lambda monitoring, see the relevant [quick start guide](/solutions/observability/apps/monitoring-aws-lambda-functions.md). :::{image} ../../../images/observability-lambda-overview.png :alt: lambda overview diff --git a/raw-migrated-files/observability-docs/observability/apm-reduce-apm-storage.md b/raw-migrated-files/observability-docs/observability/apm-reduce-apm-storage.md index 5e946eddfc..29073c946d 100644 --- a/raw-migrated-files/observability-docs/observability/apm-reduce-apm-storage.md +++ b/raw-migrated-files/observability-docs/observability/apm-reduce-apm-storage.md @@ -16,7 +16,7 @@ See [Transaction sampling](../../../solutions/observability/apps/transaction-sam In some cases, APM agents may collect large amounts of very similar or identical spans in a transaction. These repeated, similar spans often don’t provide added benefit, especially if they are of very short duration. Span compression takes these similar spans and compresses them into a single span-- retaining important information but reducing processing and storage overhead. -See [Span compression](https://www.elastic.co/guide/en/observability/current/apm-data-model-spans.html#apm-spans-span-compression) to learn more. +See [Span compression](/solutions/observability/apps/spans.md#apm-spans-span-compression) to learn more. ## Reduce collected stack trace information [apm-reduce-stacktrace] diff --git a/raw-migrated-files/observability-docs/observability/apm-service-maps.md b/raw-migrated-files/observability-docs/observability/apm-service-maps.md index d3404ca49c..bcbf4993f5 100644 --- a/raw-migrated-files/observability-docs/observability/apm-service-maps.md +++ b/raw-migrated-files/observability-docs/observability/apm-service-maps.md @@ -15,7 +15,7 @@ We currently surface two types of service maps: ## How do service maps work? [service-maps-how] -Service Maps rely on distributed traces to draw connections between services. As [distributed tracing](https://www.elastic.co/guide/en/apm/guide/current/apm-distributed-tracing.html) is enabled out-of-the-box for supported technologies, so are service maps. However, if a service isn’t instrumented, or a `traceparent` header isn’t being propagated to it, distributed tracing will not work, and the connection will not be drawn on the map. +Service Maps rely on distributed traces to draw connections between services. As [distributed tracing](/solutions/observability/apps/traces.md) is enabled out-of-the-box for supported technologies, so are service maps. However, if a service isn’t instrumented, or a `traceparent` header isn’t being propagated to it, distributed tracing will not work, and the connection will not be drawn on the map. ## Visualize your architecture [visualize-your-architecture] diff --git a/raw-migrated-files/observability-docs/observability/apm-spans.md b/raw-migrated-files/observability-docs/observability/apm-spans.md index 381fba4630..03407f6c03 100644 --- a/raw-migrated-files/observability-docs/observability/apm-spans.md +++ b/raw-migrated-files/observability-docs/observability/apm-spans.md @@ -10,7 +10,7 @@ The trace sample timeline visualization is a bird’s-eye view of what your appl View a span in detail by clicking on it in the timeline waterfall. For example, when you click on an SQL Select database query, the information displayed includes the actual SQL that was executed, how long it took, and the percentage of the trace’s total time. You also get a stack trace, which shows the SQL query in your code. Finally, APM knows which files are your code and which are just modules or libraries that you’ve installed. These library frames will be minimized by default in order to show you the most relevant stack trace. ::::{tip} -A [span](https://www.elastic.co/guide/en/apm/guide/current/data-model-spans.html) is the duration of a single event. Spans are automatically captured by APM agents, and you can also define custom spans. Each span has a type and is defined by a different color in the timeline/waterfall visualization. +A [span](/solutions/observability/apps/spans.md) is the duration of a single event. Spans are automatically captured by APM agents, and you can also define custom spans. Each span has a type and is defined by a different color in the timeline/waterfall visualization. :::: diff --git a/raw-migrated-files/observability-docs/observability/apm-transactions.md b/raw-migrated-files/observability-docs/observability/apm-transactions.md index d3b8e532c7..67fcbe6728 100644 --- a/raw-migrated-files/observability-docs/observability/apm-transactions.md +++ b/raw-migrated-files/observability-docs/observability/apm-transactions.md @@ -1,7 +1,7 @@ # Transactions [apm-transactions] ::::{tip} -A [transaction](https://www.elastic.co/guide/en/apm/guide/current/data-model-transactions.html) describes an event captured by an Elastic APM agent instrumenting a service. APM agents automatically collect performance metrics on HTTP requests, database queries, and much more. +A [transaction](/solutions/observability/apps/transactions.md) describes an event captured by an Elastic APM agent instrumenting a service. APM agents automatically collect performance metrics on HTTP requests, database queries, and much more. :::: diff --git a/raw-migrated-files/observability-docs/observability/application-logs.md b/raw-migrated-files/observability-docs/observability/application-logs.md index 054dffb3e4..8545d072cf 100644 --- a/raw-migrated-files/observability-docs/observability/application-logs.md +++ b/raw-migrated-files/observability-docs/observability/application-logs.md @@ -86,6 +86,6 @@ Learn more about log correlation in the agent-specific ingestion guides: * [Go](https://www.elastic.co/guide/en/apm/agent/go/current/logs.html) * [Java](https://www.elastic.co/guide/en/apm/agent/java/current/logs.html#log-correlation-ids) * [.NET](https://www.elastic.co/guide/en/apm/agent/dotnet/current/logs.html) -* [Node.js](https://www.elastic.co/guide/en/apm/agent/nodejs/current/log-correlation.html) +* [Node.js](https://www.elastic.co/guide/en/apm/agent/nodejs/current/logs.html) * [Python](https://www.elastic.co/guide/en/apm/agent/python/current/logs.html#log-correlation-ids) * [Ruby](https://www.elastic.co/guide/en/apm/agent/ruby/current/log-correlation.html) diff --git a/raw-migrated-files/observability-docs/observability/logs-plaintext.md b/raw-migrated-files/observability-docs/observability/logs-plaintext.md index 5c2296ea43..85f0facd6d 100644 --- a/raw-migrated-files/observability-docs/observability/logs-plaintext.md +++ b/raw-migrated-files/observability-docs/observability/logs-plaintext.md @@ -335,7 +335,7 @@ Learn about correlating plaintext logs in the agent-specific ingestion guides: * [Go](https://www.elastic.co/guide/en/apm/agent/go/current/logs.html) * [Java](https://www.elastic.co/guide/en/apm/agent/java/current/logs.html#log-correlation-ids) * [.NET](https://www.elastic.co/guide/en/apm/agent/dotnet/current/logs.html) -* [Node.js](https://www.elastic.co/guide/en/apm/agent/nodejs/current/log-correlation.html) +* [Node.js](https://www.elastic.co/guide/en/apm/agent/nodejs/current/logs.html) * [Python](https://www.elastic.co/guide/en/apm/agent/python/current/logs.html#log-correlation-ids) * [Ruby](https://www.elastic.co/guide/en/apm/agent/ruby/current/log-correlation.html) diff --git a/raw-migrated-files/security-docs/security/network-page-overview.md b/raw-migrated-files/security-docs/security/network-page-overview.md index 0aea9ec034..fa76e54d65 100644 --- a/raw-migrated-files/security-docs/security/network-page-overview.md +++ b/raw-migrated-files/security-docs/security/network-page-overview.md @@ -47,7 +47,7 @@ There are also tabs for viewing and investigating specific types of data: * **Events**: All network events. To display alerts received from external monitoring tools, scroll down to the events table and select **Show only external alerts** on the right. * **Flows**: Source and destination IP addresses and countries. * **DNS**: DNS network queries. -* **HTTP**: Received HTTP requests (HTTP requests for applications using [Elastic APM](https://www.elastic.co/guide/en/observability/current/apm.html) are monitored by default). +* **HTTP**: Received HTTP requests (HTTP requests for applications using [Elastic APM](/solutions/observability/apps/application-performance-monitoring-apm.md) are monitored by default). * **TLS**: Handshake details. * **Anomalies**: Anomalies discovered by [machine learning jobs](../../../solutions/security/advanced-entity-analytics/anomaly-detection.md). diff --git a/raw-migrated-files/stack-docs/elastic-stack/air-gapped-install.md b/raw-migrated-files/stack-docs/elastic-stack/air-gapped-install.md index 35c4423798..976a4aa7c9 100644 --- a/raw-migrated-files/stack-docs/elastic-stack/air-gapped-install.md +++ b/raw-migrated-files/stack-docs/elastic-stack/air-gapped-install.md @@ -110,8 +110,8 @@ To learn more about installing {{fleet-server}}, refer to the [{{fleet-server}} Air-gapped setup of the APM server is possible in two ways: -* By setting up one of the {{agent}} deployments with an APM integration, as described in [Switch a self-installation to the APM integration](https://www.elastic.co/guide/en/apm/guide/current/apm-integration-upgrade-steps.html). -* Or, by installing a standalone Elastic APM Server, as described in the [APM configuration documentation](https://www.elastic.co/guide/en/apm/guide/current/configuring-howto-apm-server.html). +* By setting up one of the {{agent}} deployments with an APM integration, as described in [Switch a self-installation to the APM integration](/solutions/observability/apps/switch-self-installation-to-apm-integration.md). +* Or, by installing a standalone Elastic APM Server, as described in the [APM configuration documentation](/solutions/observability/apps/configure-apm-server.md). #### 1.8. {{ems}} [air-gapped-elastic-maps-service] diff --git a/raw-migrated-files/stack-docs/elastic-stack/upgrading-elastic-stack.md b/raw-migrated-files/stack-docs/elastic-stack/upgrading-elastic-stack.md index 103825b7d6..1b2262cb3a 100644 --- a/raw-migrated-files/stack-docs/elastic-stack/upgrading-elastic-stack.md +++ b/raw-migrated-files/stack-docs/elastic-stack/upgrading-elastic-stack.md @@ -15,7 +15,7 @@ Upgrading from a release candidate build, such as 8.0.0-rc1 or 8.0.0-rc2, is not 1. Review the breaking changes for each product you use and make the necessary changes so your code is compatible with 9.0.0-beta1: - * [APM breaking changes](https://www.elastic.co/guide/en/apm/guide/current/apm-breaking.html) + * [APM breaking changes](https://www.elastic.co/guide/en/observability/current/apm-breaking.html) * [{{beats}} breaking changes](https://www.elastic.co/guide/en/beats/libbeat/current/breaking-changes.html) * [{{es}} migration guide](https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking-changes.html) * [{{elastic-sec}} release notes](https://www.elastic.co/guide/en/security/current/release-notes.html) diff --git a/raw-migrated-files/tech-content/starting-with-the-elasticsearch-platform-and-its-solutions/troubleshooting-and-faqs.md b/raw-migrated-files/tech-content/starting-with-the-elasticsearch-platform-and-its-solutions/troubleshooting-and-faqs.md index ce2737b8a1..8edfd16576 100644 --- a/raw-migrated-files/tech-content/starting-with-the-elasticsearch-platform-and-its-solutions/troubleshooting-and-faqs.md +++ b/raw-migrated-files/tech-content/starting-with-the-elasticsearch-platform-and-its-solutions/troubleshooting-and-faqs.md @@ -39,9 +39,7 @@ Throughout the Elastic docs we have a number of troubleshooting and frequently a **{{observability}}** * [Observability troubleshooting](../../../troubleshoot/observability.md) -* [APM troubleshooting](https://www.elastic.co/guide/en/apm/guide/current/troubleshoot-apm.html) -* [Legacy APM Overview troubleshooting](https://www.elastic.co/guide/en/apm/get-started/7.15/troubleshooting.html) -* [Legacy APM Server Reference troubleshooting](https://www.elastic.co/guide/en/apm/guide/current/troubleshooting.html) +* [APM troubleshooting](/troubleshoot/observability/apm.md) * [{{apm-go-agent}} troubleshooting](../../../troubleshoot/observability/apm-agent-go/apm-go-agent.md) * [{{apm-ios-agent}} troubleshooting](../../../troubleshoot/observability/apm-agent-swift/apm-ios-agent.md) * [{{apm-java-agent}} troubleshooting](../../../troubleshoot/observability/apm-agent-java/apm-java-agent.md) diff --git a/solutions/observability/apps/apm-agent-central-configuration.md b/solutions/observability/apps/apm-agent-central-configuration.md index 367b0519d4..3f229e2cd1 100644 --- a/solutions/observability/apps/apm-agent-central-configuration.md +++ b/solutions/observability/apps/apm-agent-central-configuration.md @@ -71,5 +71,5 @@ Real User Monitoring (RUM) agent For most users, APM agent configuration should work out-of-the-box. If you run into trouble, it may be because you’re not using the {{es}} output, or because your {{es}} credentials don’t have sufficient privileges. -See [configure APM agent configuration](https://www.elastic.co/guide/en/apm/guide/current/configure-agent-config.html) to learn how to configure APM Server to avoid these problems. +See [configure APM agent configuration](/solutions/observability/apps/configure-apm-agent-central-configuration.md) to learn how to configure APM Server to avoid these problems. diff --git a/solutions/observability/apps/spans.md b/solutions/observability/apps/spans.md index c3d062094f..03f3113c04 100644 --- a/solutions/observability/apps/spans.md +++ b/solutions/observability/apps/spans.md @@ -13,4 +13,8 @@ mapped_urls: % Use migrated content from existing pages that map to this page: % - [ ] ./raw-migrated-files/observability-docs/observability/apm-data-model-spans.md -% - [ ] ./raw-migrated-files/docs-content/serverless/observability-apm-compress-spans.md \ No newline at end of file +% - [ ] ./raw-migrated-files/docs-content/serverless/observability-apm-compress-spans.md + +% Internal links rely on the following IDs being on this page (e.g. as a heading ID, paragraph ID, etc): + +$$$apm-spans-span-compression$$$ \ No newline at end of file diff --git a/solutions/observability/apps/storage-explorer.md b/solutions/observability/apps/storage-explorer.md index cd702c6a76..148e15ccf4 100644 --- a/solutions/observability/apps/storage-explorer.md +++ b/solutions/observability/apps/storage-explorer.md @@ -15,7 +15,7 @@ Analyze your APM data and manage costs with **storage explorer**. For example, a ## Index lifecycle phases [_index_lifecycle_phases] -A default [index lifecycle policy](https://www.elastic.co/guide/en/apm/guide/current/ilm-how-to.html) is applied to each APM data stream, but can be customized depending on your business needs. Use the **Index lifecycle phase** dropdown to visualize and analyze your storage by phase. +A default [index lifecycle policy](/solutions/observability/apps/index-lifecycle-management.md) is applied to each APM data stream, but can be customized depending on your business needs. Use the **Index lifecycle phase** dropdown to visualize and analyze your storage by phase. Customizing the default APM index lifecycle policies can save money by specifying things like: @@ -23,7 +23,7 @@ Customizing the default APM index lifecycle policies can save money by specifyin * The point at which availability is not as critical and the number of replicas can be reduced. * When the index can be safely deleted. -See [Index lifecycle management](https://www.elastic.co/guide/en/apm/guide/current/ilm-how-to.html) to learn more about customizing the default APM index lifecycle policies. +See [Index lifecycle management](/solutions/observability/apps/index-lifecycle-management.md) to learn more about customizing the default APM index lifecycle policies. ## Service size chart [_service_size_chart] @@ -50,12 +50,12 @@ As you explore your service statistics, you might want to take action to reduce ### Reduce the number of transactions [_reduce_the_number_of_transactions] -To reduce the number of transactions a service generates, configure a more aggressive [transaction sampling policy](https://www.elastic.co/guide/en/apm/guide/current/sampling.html). Transaction sampling lowers the amount of data ingested without negatively impacting the usefulness of your data. +To reduce the number of transactions a service generates, configure a more aggressive [transaction sampling policy](/solutions/observability/apps/transaction-sampling.md). Transaction sampling lowers the amount of data ingested without negatively impacting the usefulness of your data. ### Reduce the number of spans [_reduce_the_number_of_spans] -To reduce the number of spans a service generates, enable [span compression](https://www.elastic.co/guide/en/apm/guide/current/span-compression.html). Span compression saves on data and transfer costs by compressing multiple, similar spans into a single span. +To reduce the number of spans a service generates, enable [span compression](/solutions/observability/apps/spans.md#apm-spans-span-compression). Span compression saves on data and transfer costs by compressing multiple, similar spans into a single span. ### Reduce the number of metrics [_reduce_the_number_of_metrics] diff --git a/troubleshoot/kibana/using-kibana-server-logs.md b/troubleshoot/kibana/using-kibana-server-logs.md index 7f6ac6daf3..693518f1b9 100644 --- a/troubleshoot/kibana/using-kibana-server-logs.md +++ b/troubleshoot/kibana/using-kibana-server-logs.md @@ -40,17 +40,17 @@ logging.loggers: ``` ::::{warning} -Kibana’s `file` appender is configured to produce logs in [ECS JSON](https://www.elastic.co/guide/en/ecs/{{ecs_version}}/ecs-reference.html) format. It’s the only format that includes the meta information necessary for [log correlation](https://www.elastic.co/guide/en/apm/agent/nodejs/current/log-correlation.html) out-of-the-box. +Kibana’s `file` appender is configured to produce logs in [ECS JSON](https://www.elastic.co/guide/en/ecs/{{ecs_version}}/ecs-reference.html) format. It’s the only format that includes the meta information necessary for [log correlation](https://www.elastic.co/guide/en/apm/agent/nodejs/current/logs.html) out-of-the-box. :::: -The next step is to define what [observability tools](https://www.elastic.co/observability) are available. For a better experience, set up an [Observability integration](https://www.elastic.co/guide/en/apm/get-started/current/observability-integrations.html) provided by Elastic to debug your application with the [APM UI.](#debugging-logs-apm-ui) To debug something quickly without setting up additional tooling, you can work with [the plain {{kib}} logs.](#plain-kibana-logs) +The next step is to define what [observability tools](https://www.elastic.co/observability) are available. For a better experience, set up an [Observability integration](/solutions/observability/logs/stream-application-logs.md) provided by Elastic to debug your application with the [APM UI.](#debugging-logs-apm-ui) To debug something quickly without setting up additional tooling, you can work with [the plain {{kib}} logs.](#plain-kibana-logs) ## APM UI [debugging-logs-apm-ui] **Prerequisites** {{kib}} logs are configured to be in [ECS JSON](https://www.elastic.co/guide/en/ecs/{{ecs_version}}/ecs-reference.html) format to include tracing identifiers. -To debug {{kib}} with the APM UI, you must set up the APM infrastructure. You can find instructions for the setup process [on the Observability integrations page](https://www.elastic.co/guide/en/apm/get-started/current/observability-integrations.html). +To debug {{kib}} with the APM UI, you must set up the APM infrastructure. You can find instructions for the setup process [on the Observability integrations page](/solutions/observability/logs/stream-application-logs.md). Once you set up the APM infrastructure, you can enable the APM agent and put {{kib}} under load to collect APM events. To analyze the collected metrics and logs, use the APM UI as demonstrated [in the docs](../../solutions/observability/apps/transactions-2.md#transaction-trace-sample). diff --git a/troubleshoot/observability/apm-agent-nodejs/apm-nodejs-agent.md b/troubleshoot/observability/apm-agent-nodejs/apm-nodejs-agent.md index ca18dbca8f..faa6fd1195 100644 --- a/troubleshoot/observability/apm-agent-nodejs/apm-nodejs-agent.md +++ b/troubleshoot/observability/apm-agent-nodejs/apm-nodejs-agent.md @@ -10,20 +10,20 @@ Is something not working as expected? Don’t worry if you can’t figure out wh If you’re an existing Elastic customer with a support contract, please create a ticket in the [Elastic Support portal](https://support.elastic.co/customers/s/login/). Other users can post in the [APM discuss forum](https://discuss.elastic.co/c/apm). -::::{important} +::::{important} **Please upload your complete debug logs** to a service like [GitHub Gist](https://gist.github.com) so that we can analyze the problem. Logs should include everything from when the application starts up until the first request executes. See [Debug mode](#debug-mode) for more information. :::: -## Updating to latest agent version [use-latest-agent] +## Updating to latest agent version [use-latest-agent] The Elastic Node.js APM Agent is updated frequently and releases are not strongly tied to other components in the Elastic Stack. Therefore, updating to the most recently released agent version is often the recommended first troubleshooting step. See [upgrading documentation](https://www.elastic.co/guide/en/apm/agent/nodejs/current/upgrading.html) for more details. -## Debug mode [debug-mode] +## Debug mode [debug-mode] To capture enough information for troubleshooting, perform these steps: @@ -41,10 +41,10 @@ ELASTIC_APM_LOG_LEVEL=trace ELASTIC_APM_LOGGER=false node app.js | tee -a apm-de If you are capturing debugging output for Elastic support, for help on the Elastic forums, or for a GitHub issue, **please upload the complete debug output** to a service like [GitHub Gist](https://gist.github.com) so that we can analyze the problem. -## Common problems [common-problems] +## Common problems [common-problems] -### No data is sent to the APM Server [no-data-sent] +### No data is sent to the APM Server [no-data-sent] If there is no data for your service in the Kibana APM app, check the log output for messages like the following. @@ -54,7 +54,7 @@ The most common source of problems are connection issues between the agent and t APM Server transport error (ECONNREFUSED): connect ECONNREFUSED 127.0.0.1:8200 ``` -These may indicate an issue with the agent configuration (see [`serverUrl`](https://www.elastic.co/guide/en/apm/agent/nodejs/current/configuration.html#server-url), [`secretToken`](https://www.elastic.co/guide/en/apm/agent/nodejs/current/configuration.html#secret-token) or [`apiKey`](https://www.elastic.co/guide/en/apm/agent/nodejs/current/configuration.html#api-key)), a network problem between agent and server, or that the APM server is down or misconfigured (see [the APM server troubleshooting docs](https://www.elastic.co/guide/en/apm/guide/current/troubleshooting.html)). +These may indicate an issue with the agent configuration (see [`serverUrl`](https://www.elastic.co/guide/en/apm/agent/nodejs/current/configuration.html#server-url), [`secretToken`](https://www.elastic.co/guide/en/apm/agent/nodejs/current/configuration.html#secret-token) or [`apiKey`](https://www.elastic.co/guide/en/apm/agent/nodejs/current/configuration.html#api-key)), a network problem between agent and server, or that the APM server is down or misconfigured (see [the APM server troubleshooting docs](/troubleshoot/observability/apm.md)). Also look for error messages starting with `Elastic APM ...`. Some examples: @@ -69,14 +69,14 @@ Elastic APM is incorrectly configured: serverUrl "..." contains an invalid port! ``` -### No metrics or trace data is sent to APM Server [missing-performance-metrics] +### No metrics or trace data is sent to APM Server [missing-performance-metrics] Errors get tracked just fine, but you don’t see any performance metrics or trace data. Make sure that the agent is **both required and started at the very top of your main app file** (usually the `index.js`, `server.js` or `app.js` file). It’s important that the agent is started before any other modules are `require`d. If not, the agent will not be able to hook into any modules and will not be able to measure the performance of your application. See [Start gotchas](https://www.elastic.co/guide/en/apm/agent/nodejs/current/starting-the-agent.html#start-gotchas) for a number of possible surprises in correctly starting the APM agent when used with some compilers or bundlers. -## Disable the Agent [disable-agent] +## Disable the Agent [disable-agent] In the unlikely event the agent causes disruptions to a production application, you can disable the agent while you troubleshoot.