Updates links pointing to integration docs (#838)

## Description

Related to #673

This PR updates the links that point to the `integration-docs` repo from
`asciidocalypse://docs/integration-docs/docs/reference/` to
`integration-docs://reference/`.

Author: szabosteve

manage-data/ingest/tools.md

@@ -41,7 +41,7 @@ Depending on the type of data you want to ingest, you have a number of methods a
 
 | Tools   | Usage           | Links to more information |
 | ------- | --------------- | ------------------------- |
-| Integrations | Ingest data using a variety of Elastic integrations. | [Elastic Integrations](asciidocalypse://docs/integration-docs/docs/reference/index.md) |
+| Integrations | Ingest data using a variety of Elastic integrations. | [Elastic Integrations](integration-docs://reference/index.md) |
 | File upload | Upload data from a file and inspect it before importing it into {{es}}. | [Upload data files](/manage-data/ingest/upload-data-files.md) |
 | APIs  | Ingest data through code by using the APIs of one of the language clients or the {{es}} HTTP APIs. | [Document APIs](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-document) |
 | OpenTelemetry | Collect and send your telemetry data to Elastic Observability | [Elastic Distributions of OpenTelemetry](https://github.com/elastic/opentelemetry?tab=readme-ov-file#elastic-distributions-of-opentelemetry) |

raw-migrated-files/docs-content/serverless/project-setting-data.md

@@ -11,7 +11,7 @@ Access to individual features is governed by Elastic user roles. Consult your ad
 
 | Feature | Description | Available in |
 | --- | --- | --- |
-| [Integrations](asciidocalypse://docs/integration-docs/docs/reference/index.md) | Connect your data to your project. | [![Observability](../../../images/serverless-obs-badge.svg "")](../../../solutions/observability.md)[![Security](../../../images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) |
+| [Integrations](integration-docs://reference/index.md) | Connect your data to your project. | [![Observability](../../../images/serverless-obs-badge.svg "")](../../../solutions/observability.md)[![Security](../../../images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) |
 | [Fleet and Elastic Agent](/reference/ingestion-tools/fleet/index.md) | Add monitoring for logs, metrics, and other types of data to a host. | [![Observability](../../../images/serverless-obs-badge.svg "")](../../../solutions/observability.md)[![Security](../../../images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) |
 | [{{data-sources-cap}}](../../../explore-analyze/find-and-organize/data-views.md) | Manage the fields in the data views that retrieve your data from {{es-serverless}}. | [![Elasticsearch](../../../images/serverless-es-badge.svg "")](../../../solutions/search.md)[![Observability](../../../images/serverless-obs-badge.svg "")](../../../solutions/observability.md)[![Security](../../../images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) |
 | [Index management](../../../manage-data/data-store/index-basics.md) | View index settings, mappings, and statistics and perform operations on indices. | [![Elasticsearch](../../../images/serverless-es-badge.svg "")](../../../solutions/search.md)[![Observability](../../../images/serverless-obs-badge.svg "")](../../../solutions/observability.md)[![Security](../../../images/serverless-sec-badge.svg "")](../../../solutions/security/elastic-security-serverless.md) |

reference/ingestion-tools/fleet/config-file-example-apache.md

@@ -76,7 +76,7 @@ inputs: <7>
 9. For available input types, refer to [{{agent}} inputs](/reference/ingestion-tools/fleet/elastic-agent-inputs-list.md).
 10. Learn about [Data streams](/reference/ingestion-tools/fleet/data-streams.md) for time series data.
 11. Specify a unique ID for each individual input stream. Naming the ID by appending the associated `data_stream` dataset (for example `{{user-defined-unique-id}}-apache.access` or `{{user-defined-unique-id}}-apache.error`) is a recommended practice, but any unique ID will work.
-12. Refer to [Logs](asciidocalypse://docs/integration-docs/docs/reference/apache.md#apache-logs) in the Apache HTTP Server integration documentation for the logs available to ingest and exported fields.
+12. Refer to [Logs](integration-docs://reference/apache/index.md) in the Apache HTTP Server integration documentation for the logs available to ingest and exported fields.
 13. Path to the log files to be monitored.
 
 
@@ -128,7 +128,7 @@ inputs: <7>
 9. Learn about [Data streams](/reference/ingestion-tools/fleet/data-streams.md) for time series data.
 10. Specify a unique ID for each individual input stream. Naming the ID by appending the associated `data_stream` dataset (for example `{{user-defined-unique-id}}-apache.status`) is a recommended practice, but any unique ID will work.
 11. A user-defined dataset. You can specify anything that makes sense to signify the source of the data.
-12. Refer to [Metrics](asciidocalypse://docs/integration-docs/docs/reference/apache.md#apache-metrics) in the Apache HTTP Server integration documentation for the type of metrics collected and exported fields.
+12. Refer to [Metrics](integration-docs://reference/apache/index.md) in the Apache HTTP Server integration documentation for the type of metrics collected and exported fields.
 
 
 

reference/ingestion-tools/fleet/config-file-example-nginx.md

@@ -81,7 +81,7 @@ inputs: <7>
 9. For available input types, refer to [{{agent}} inputs](/reference/ingestion-tools/fleet/elastic-agent-inputs-list.md).
 10. Learn about [Data streams](/reference/ingestion-tools/fleet/data-streams.md) for time series data.
 11. Specify a unique ID for each individual input stream. Naming the ID by appending the associated `data_stream` dataset (for example `{{user-defined-unique-id}}-nginx.access` or `{{user-defined-unique-id}}-nginx.error`) is a recommended practice, but any unique ID will work.
-12. Refer to [Logs reference](asciidocalypse://docs/integration-docs/docs/reference/nginx.md#nginx-logs-reference) in the Nginx HTTP integration documentation for the logs available to ingest and exported fields.
+12. Refer to [Logs reference](integration-docs://reference/nginx/index.md#logs-reference) in the Nginx HTTP integration documentation for the logs available to ingest and exported fields.
 13. Path to the log files to be monitored.
 
 
@@ -135,7 +135,7 @@ inputs: <7>
 10. Learn about [Data streams](/reference/ingestion-tools/fleet/data-streams.md) for time series data.
 11. Specify a unique ID for each individual input stream. Naming the ID by appending the associated `data_stream` dataset (for example `{{user-defined-unique-id}}-nginx.stubstatus`) is a recommended practice, but any unique ID will work.
 12. A user-defined dataset. You can specify anything that makes sense to signify the source of the data.
-13. Refer to [Metrics reference](asciidocalypse://docs/integration-docs/docs/reference/nginx.md#nginx-metrics-reference) in the Nginx integration documentation for the type of metrics collected and exported fields.
+13. Refer to [Metrics reference](integration-docs://reference/nginx/index.md#metrics-reference) in the Nginx integration documentation for the type of metrics collected and exported fields.
 
 
 

reference/ingestion-tools/fleet/configuring-kubernetes-metadata.md

@@ -7,7 +7,7 @@ mapped_pages:
 
 Kubernetes [metadata](/solutions/observability/infra-and-hosts/tutorial-observe-kubernetes-deployments.md#beats-metadata) refer to contextual information extracted from Kubernetes resources. Metadata information enrich metrics and logs collected from a Kubernetes cluster, enabling deeper insights into Kubernetes environments.
 
-When the {{agent}}'s policy includes the [{{k8s}} Integration](asciidocalypse://docs/integration-docs/docs/reference/kubernetes.md) which configures the collection of Kubernetes related metrics and container logs, the mechanisms used for the metadata enrichment are:
+When the {{agent}}'s policy includes the [{{k8s}} Integration](integration-docs://reference/kubernetes.md) which configures the collection of Kubernetes related metrics and container logs, the mechanisms used for the metadata enrichment are:
 
 * [Kubernetes Provider](/reference/ingestion-tools/fleet/kubernetes-provider.md) for log collection
 * Kubernetes metadata enrichers for metrics

reference/ingestion-tools/fleet/dissect-processor.md

@@ -83,5 +83,5 @@ This configuration produces fields like:
 
 `service.name` is an ECS [keyword field](elasticsearch://reference/elasticsearch/mapping-reference/keyword.md), which means that you can use it in {{es}} for filtering, sorting, and aggregations.
 
-When possible, use ECS-compatible field names. For more information, see the [Elastic Common Schema](asciidocalypse://docs/integration-docs/docs/reference/index.md) documentation.
+When possible, use ECS-compatible field names. For more information, see the [Elastic Common Schema](integration-docs://reference/index.md) documentation.
 

reference/ingestion-tools/fleet/elastic-agent-unprivileged.md

@@ -100,12 +100,12 @@ As well, a warning is displayed in {{kib}} if you try to add an integration that
 
 Examples of integrations that require {{agent}} to have administrative privileges are:
 
-* [{{elastic-defend}}](asciidocalypse://docs/integration-docs/docs/reference/endpoint.md)
-* [Auditd Manager](asciidocalypse://docs/integration-docs/docs/reference/auditd_manager.md)
-* [File Integrity Monitoring](asciidocalypse://docs/integration-docs/docs/reference/fim.md)
-* [Network Packet Capture](asciidocalypse://docs/integration-docs/docs/reference/network_traffic.md)
-* [System Audit](asciidocalypse://docs/integration-docs/docs/reference/system_audit.md)
-* [Universal Profiling Agent](asciidocalypse://docs/integration-docs/docs/reference/profiler_agent.md)
+* [{{elastic-defend}}](integration-docs://reference/endpoint/index.md)
+* [Auditd Manager](integration-docs://reference/auditd_manager/index.md)
+* [File Integrity Monitoring](integration-docs://reference/fim/index.md)
+* [Network Packet Capture](integration-docs://reference/network_traffic/index.md)
+* [System Audit](integration-docs://reference/system_audit/index.md)
+* [Universal Profiling Agent](integration-docs://reference/profiler_agent/index.md)
 
 
 ## Viewing an {{agent}} privilege mode [unprivileged-view-mode]

reference/ingestion-tools/fleet/example-standalone-monitor-nginx-serverless.md

@@ -311,4 +311,4 @@ Congratulations! You have successfully set up monitoring for nginx using standal
 ## What’s next? [_whats_next]
 
 * Learn more about [{{fleet}} and {{agent}}](/reference/ingestion-tools/fleet/index.md).
-* Learn more about [{{integrations}}](asciidocalypse://docs/integration-docs/docs/reference/index.md).
+* Learn more about [{{integrations}}](integration-docs://reference/index.md).

reference/ingestion-tools/fleet/example-standalone-monitor-nginx.md

@@ -310,4 +310,4 @@ Congratulations! You have successfully set up monitoring for nginx using standal
 ## What’s next? [_whats_next_2]
 
 * Learn more about [{{fleet}} and {{agent}}](/reference/ingestion-tools/fleet/index.md).
-* Learn more about [{{integrations}}](asciidocalypse://docs/integration-docs/docs/reference/index.md).
+* Learn more about [{{integrations}}](integration-docs://reference/index.md).

reference/ingestion-tools/fleet/hints-annotations-autodiscovery.md

@@ -41,7 +41,7 @@ The host to use for metrics retrieval. If not defined, the host will be set as t
 
 ### `co.elastic.hints/data_stream` [_co_elastic_hintsdata_stream]
 
-The list of data streams to enable. If not specified, the integration’s default data streams are used. To find the defaults, refer to the [Elastic integrations documentation](asciidocalypse://docs/integration-docs/docs/reference/index.md).
+The list of data streams to enable. If not specified, the integration’s default data streams are used. To find the defaults, refer to the [Elastic integrations documentation](integration-docs://reference/index.md).
 
 If data streams are specified, additional hints can be defined per data stream. For example, `co.elastic.hints/info.period: 5m` if the data stream specified is `info` for the [Redis module](beats://reference/metricbeat/metricbeat-module-redis.md).