Skip to content

Commit c8d2068

Browse files
authored
Add links for Obs
Add links for Obs
1 parent 5fdb60e commit c8d2068

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

get-started/introduction.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -89,13 +89,13 @@ At the heart of Elastic {{observability}} are several key concepts that enable i
8989

9090
:::{dropdown} Concepts
9191
* The three pillars of {{observability}} are:
92-
* [**Logs:**](/solutions/observability/logs) Timestamped records of events that provide detailed, contextual information.
93-
* **Metrics:** Numerical measurements of system performance and health over time.
94-
* **Traces:** A representation of the end-to-end journey of a request as it travels through a distributed system.
95-
* **OpenTelemetry:** {{Observability}} offers first-class, production-grade support for OpenTelemetry. This allows organizations to use vendor-neutral instrumentation and stream native OTel data without proprietary agents, leveraging the Elastic Distribution of OpenTelemetry (EDOT).
96-
* [**AIOps and AI Assistant:**](/solutions/observability/observability-ai-assistant) Leverages predictive analytics and an LLM-powered AI Assistant to reduce the time required to detect, investigate, and resolve incidents. This includes zero-config anomaly detection, pattern analysis, and the ability to surface correlations and root causes.
97-
* **[Alerting](/solutions/observability/incident-management/alerting) and [Cases](/solutions/observability/incident-management/cases):** A built-in feature for creating rules to detect complex conditions and trigger actions. It allows teams to stay aware of potential issues and use cases to track investigation details, assign tasks, and collaborate on resolutions.
98-
* [**Service Level Objectives (SLOs):**](/solutions/observability/incident-management/service-level-objectives-slos) A framework for defining and monitoring the reliability of a service. Elastic {{observability}} allows for creating and tracking SLOs to ensure that performance targets are being met.
92+
* [**Logs:**](/solutions/observability/logs.md) Timestamped records of events that provide detailed, contextual information.
93+
* [**Metrics:**](/solutions/observability/infra-and-hosts/analyze-infrastructure-host-metrics.md) Numerical measurements of system performance and health over time.
94+
* [**Traces:**](/solutions/observability/apm/traces.md) A representation of the end-to-end journey of a request as it travels through a distributed system.
95+
* [**OpenTelemetry:**](/solutions/observability/apm/opentelemetry.md) {{Observability}} offers first-class, production-grade support for OpenTelemetry. This allows organizations to use vendor-neutral instrumentation and stream native OTel data without proprietary agents, leveraging the Elastic Distribution of OpenTelemetry (EDOT).
96+
* [**AIOps and AI Assistant:**](/solutions/observability/observability-ai-assistant.md) Leverages predictive analytics and an LLM-powered AI Assistant to reduce the time required to detect, investigate, and resolve incidents. This includes zero-config anomaly detection, pattern analysis, and the ability to surface correlations and root causes.
97+
* **[Alerting](/solutions/observability/incident-management/alerting.md) and [Cases](/solutions/observability/incident-management/cases.md):** A built-in feature for creating rules to detect complex conditions and trigger actions. It allows teams to stay aware of potential issues and use cases to track investigation details, assign tasks, and collaborate on resolutions.
98+
* [**Service Level Objectives (SLOs):**](/solutions/observability/incident-management/service-level-objectives-slos.md) A framework for defining and monitoring the reliability of a service. Elastic {{observability}} allows for creating and tracking SLOs to ensure that performance targets are being met.
9999
:::
100100

101101
## {{elastic-sec}}

0 commit comments

Comments
 (0)