Skip to content

Commit 5371a4e

Browse files
committed
Apply comments
1 parent 58c94a4 commit 5371a4e

File tree

6 files changed

+9
-9
lines changed

6 files changed

+9
-9
lines changed

solutions/observability/apm/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,4 +26,4 @@ Metrics are another vital source of information when debugging production system
2626

2727
## Give Elastic APM a try [give_elastic_apm_a_try]
2828

29-
Want to quickly spin up an APM deployment? Refer to [Get started for APM](/solutions/observability/apm/get-started.md). We recommend using the [Elastic Distributions of OpenTelemetry (EDOT)](/solutions/observability/apm/opentelemetry/index.md) as the preferred way to collect application telemetry data. To host everything yourself instead, refer to [Set up APM Server](/solutions/observability/apm/apm-server/setup.md).
29+
Want to quickly spin up an APM deployment? Refer to [Get started for APM](/solutions/observability/apm/get-started.md). We recommend using the [Elastic Distributions of OpenTelemetry (EDOT)](/solutions/observability/apm/opentelemetry/index.md) to collect application telemetry data. To host everything yourself instead, refer to [Set up APM Server](/solutions/observability/apm/apm-server/setup.md).

solutions/observability/cicd.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,10 +20,10 @@ To provide monitoring dashboards, alerting, and root cause analysis on pipelines
2020

2121
## CI/CD observability architectures [ci-cd-architecture]
2222

23-
Using the {{apm-server}}, connect all your OpenTelemetry native CI/CD tools directly to Elastic {{observability}}.
23+
Use the {{apm-server}} to connect all your OpenTelemetry native CI/CD tools directly to Elastic {{observability}}.
2424

2525
:::{tip}
26-
We recommend using the [{{edot}} Collector](opentelemetry://reference/index.md) as the preferred way to collect CI/CD observability data.
26+
We recommend using the [{{edot}} Collector](opentelemetry://reference/index.md) to collect CI/CD observability data.
2727
:::
2828

2929
:::{image} /solutions/images/observability-simple-arch-observability.png

solutions/observability/infra-and-hosts.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ products:
1818
Explore the topics in this section to learn how to observe and monitor hosts and other systems running in your environment.
1919

2020
:::{tip}
21-
We recommend using the [Elastic Distribution of OpenTelemetry (EDOT) Collector](/solutions/observability/get-started/quickstart-monitor-hosts-with-opentelemetry.md) as the preferred way to collect infrastructure metrics and logs. You can also use the [Elastic Agent](/solutions/observability/infra-and-hosts/get-started-with-system-metrics.md) with integrations for infrastructure monitoring.
21+
We recommend using the [Elastic Distribution of OpenTelemetry (EDOT) Collector](/solutions/observability/get-started/quickstart-monitor-hosts-with-opentelemetry.md) to collect infrastructure metrics and logs. You can also use the [Elastic Agent](/solutions/observability/infra-and-hosts/get-started-with-system-metrics.md) with integrations for infrastructure monitoring.
2222
:::
2323

2424
| | |

solutions/observability/infra-and-hosts/analyze-infrastructure-host-metrics.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ products:
1515
Observability allows you to visualize infrastructure metrics to help diagnose problematic spikes, identify high resource utilization, automatically discover and track pods, and unify your metrics with logs and APM data.
1616

1717
:::{tip}
18-
We recommend using the [Elastic Distribution of OpenTelemetry (EDOT) Collector](/solutions/observability/get-started/quickstart-monitor-hosts-with-opentelemetry.md) as the preferred way to collect infrastructure metrics. You can also use {{agent}} integrations to ingest and analyze metrics from servers, Docker containers, Kubernetes orchestrations, and more.
18+
We recommend using the [Elastic Distribution of OpenTelemetry (EDOT) Collector](/solutions/observability/get-started/quickstart-monitor-hosts-with-opentelemetry.md) to collect infrastructure metrics. You can also use {{agent}} integrations to ingest and analyze metrics from servers, Docker containers, {{k8s}} deployments, and more.
1919
:::
2020

2121
For more information, refer to the following links:

solutions/observability/logs/ecs-formatted-application-logs.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,10 +12,10 @@ products:
1212

1313
# ECS formatted application logs [logs-ecs-application]
1414

15-
Logs formatted in {{product.ecs}} don't require manual parsing, and the configuration can be reused across applications. ECS-formatted logs, when paired with an {{apm-agent}} or [{{edot}} SDKs](opentelemetry://reference/edot-sdks/index.md), allow you to correlate logs to easily view logs that belong to a particular trace.
15+
Logs formatted in {{product.ecs}} don't require manual parsing, and the same ingest configuration can be reused across applications. ECS-formatted logs, when paired with an {{apm-agent}} or [{{edot}} SDKs](opentelemetry://reference/edot-sdks/index.md), allow you to correlate logs to easily view logs that belong to a particular trace.
1616

1717
:::{tip}
18-
We recommend using the [{{edot}} SDKs](opentelemetry://reference/edot-sdks/index.md) as the preferred way to instrument your applications and collect ECS-formatted logs with automatic log correlation. You can also format your logs in ECS format.
18+
We recommend using the [{{edot}} SDKs](opentelemetry://reference/edot-sdks/index.md) to instrument your applications and collect ECS-formatted logs with automatic log correlation. You can also format your logs in ECS format.
1919
:::
2020

2121
You can format your logs in ECS format the following ways:

solutions/observability/logs/plaintext-application-logs.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,10 +31,10 @@ To ingest, parse, and correlate plaintext logs:
3131
Send application logs to {{es}} using one of the following shipping tools:
3232

3333
* [{{filebeat}}](/solutions/observability/logs/plaintext-application-logs.md#ingest-plaintext-logs-with-filebeat) A lightweight data shipper that sends log data to {{es}}.
34-
* [{{agent}}](/solutions/observability/logs/plaintext-application-logs.md#ingest-plaintext-logs-with-the-agent) A single agent for logs, metrics, security data, and threat prevention. Combined with {{fleet}}, you can centrally manage {{agent}} policies and lifecycles directly from {{kib}}.
34+
* [{{agent}}](/solutions/observability/logs/plaintext-application-logs.md#ingest-plaintext-logs-with-the-agent) A single agent that can collect logs, metrics, and security data, and protect your hosts. You can use {{fleet}} to manage {{agent}} policies and lifecycles directly from {{kib}}.
3535

3636
:::{tip}
37-
We recommend using the [{{edot}} Collector](/solutions/observability/logs/stream-any-log-file-using-edot-collector.md) as the preferred way to collect application logs.
37+
We recommend using the [{{edot}} Collector](/solutions/observability/logs/stream-any-log-file-using-edot-collector.md) to collect application logs.
3838
:::
3939

4040

0 commit comments

Comments
 (0)