You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: solutions/observability/apps.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,8 +15,8 @@ Explore the topics in this section to learn how to observe and monitor software
15
15
16
16
|||
17
17
| --- | --- |
18
-
|[Application performance monitoring (APM)](../../../solutions/observability/apps/application-performance-monitoring-apm.md)| 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. |
19
-
|[Synthetic monitoring](../../../solutions/observability/apps/synthetic-monitoring.md)| Monitor the availability of network endpoints and services. |
20
-
|[Real user monitoring](../../../solutions/observability/apps/real-user-monitoring-user-experience.md)| Quantify and analyze the perceived performance of your web application using real-world user experiences. |
21
-
|[Uptime monitoring (deprecated)](../../../solutions/observability/apps/uptime-monitoring-deprecated.md)| Periodically check the status of your services and applications. |
22
-
|[Tutorial: Monitor a Java application](../../../solutions/observability/apps/tutorial-monitor-java-application.md)| Monitor a Java application using Elastic Observability: Logs, Infrastructure metrics, APM, and Uptime. |
18
+
|[Application performance monitoring (APM)](../../solutions/observability/apps/application-performance-monitoring-apm.md)| 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. |
19
+
|[Synthetic monitoring](../../solutions/observability/apps/synthetic-monitoring.md)| Monitor the availability of network endpoints and services. |
20
+
|[Real user monitoring](../../solutions/observability/apps/real-user-monitoring-user-experience.md)| Quantify and analyze the perceived performance of your web application using real-world user experiences. |
21
+
|[Uptime monitoring (deprecated)](../../solutions/observability/apps/uptime-monitoring-deprecated.md)| Periodically check the status of your services and applications. |
22
+
|[Tutorial: Monitor a Java application](../../solutions/observability/apps/tutorial-monitor-java-application.md)| Monitor a Java application using Elastic Observability: Logs, Infrastructure metrics, APM, and Uptime. |
Copy file name to clipboardExpand all lines: solutions/observability/data-set-quality-monitoring.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,9 +27,9 @@ The quality of your data sets is based on the percentage of degraded documents i
27
27
28
28
From the data set table, you’ll find information for each data set such as its namespace, when the data set was last active, and the percentage of degraded docs. The percentage of degraded documents determines the data set’s quality according to the following scale:
29
29
30
-
* Good (): 0% of the documents in the data set are degraded.
31
-
* Degraded (): Greater than 0% and up to 3% of the documents in the data set are degraded.
32
-
* Poor (): Greater than 3% of the documents in the data set are degraded.
30
+
* Good (): 0% of the documents in the data set are degraded.
31
+
* Degraded (): Greater than 0% and up to 3% of the documents in the data set are degraded.
32
+
* Poor (): Greater than 3% of the documents in the data set are degraded.
33
33
34
34
Opening the details of a specific data set shows the degraded documents history, a summary for the data set, and other details that can help you determine if you need to investigate any issues.
35
35
@@ -43,7 +43,7 @@ The Data Set Quality page has a couple of different ways to help you find ignore
43
43
44
44
To open the details page for a data set with poor or degraded quality and view ignored fields:
45
45
46
-
1. From the data set table, click  next to a data set with poor or degraded quality.
46
+
1. From the data set table, click  next to a data set with poor or degraded quality.
47
47
2. From the details, scroll down to **Quality issues**.
48
48
49
49
The **Quality issues** section shows fields that have been ignored, the number of documents that contain ignored fields, and the timestamp of last occurrence of the field being ignored.
@@ -60,7 +60,7 @@ The **Documents** table in Logs Explorer or Discover is automatically filtered t
60
60
61
61
Now that you know which documents contain ignored fields, examine them more closely to find the origin of the issue:
62
62
63
-
1. Under the **actions** column, click  to open the document details.
63
+
1. Under the **actions** column, click  to open the document details.
64
64
2. Select the **JSON** tab.
65
65
3. Scroll towards the end of the JSON to find the `ignored_field_values`.
## Get started with your use case [get-started-with-use-case]
26
26
27
27
Learn how to spin up a deployment of our hosted {{ess}} or create an Observability serverless project and use Elastic Observability to gain deeper insight into the behavior of your applications and systems.
@@ -35,7 +35,7 @@ Learn how to spin up a deployment of our hosted {{ess}} or create an Observabili
35
35
3.**View your data.** Navigate seamlessly between Observabilty UIs and dashboards to identify and resolve problems quickly.
36
36
4.**Customize.** Expand your deployment and add features like alerting and anomaly detection.
37
37
38
-
To get started with on serverless, [create an Observability project](../../../solutions/observability/get-started/create-an-observability-project.md), then follow one of our [quickstarts](../../../solutions/observability/get-started.md#quickstarts-overview) to learn how to ingest and visualize your observability data.
38
+
To get started with on serverless, [create an Observability project](../../solutions/observability/get-started/create-an-observability-project.md), then follow one of our [quickstarts](../../solutions/observability/get-started.md#quickstarts-overview) to learn how to ingest and visualize your observability data.
39
39
40
40
### Quickstarts [quickstarts-overview]
41
41
@@ -48,11 +48,11 @@ Our quickstarts dramatically reduce your time-to-value by offering a fast path t
48
48
49
49
Follow the steps in these guides to get started quickly:
50
50
51
-
*[Quickstart: Monitor hosts with {{agent}}](../../../solutions/observability/get-started/quickstart-monitor-hosts-with-elastic-agent.md)
52
-
*[Quickstart: Monitor your Kubernetes cluster with {{agent}}](../../../solutions/observability/get-started/quickstart-monitor-kubernetes-cluster-with-elastic-agent.md)
53
-
*[Quickstart: Monitor hosts with OpenTelemetry](../../../solutions/observability/get-started/quickstart-monitor-hosts-with-opentelemetry.md)
54
-
*[Quickstart: Unified Kubernetes Observability with Elastic Distributions of OpenTelemetry (EDOT)](../../../solutions/observability/get-started/quickstart-unified-kubernetes-observability-with-elastic-distributions-of-opentelemetry-edot.md)
55
-
*[Quickstart: Collect data with AWS Firehose](../../../solutions/observability/get-started/quickstart-collect-data-with-aws-firehose.md)
51
+
*[Quickstart: Monitor hosts with {{agent}}](../../solutions/observability/get-started/quickstart-monitor-hosts-with-elastic-agent.md)
52
+
*[Quickstart: Monitor your Kubernetes cluster with {{agent}}](../../solutions/observability/get-started/quickstart-monitor-kubernetes-cluster-with-elastic-agent.md)
53
+
*[Quickstart: Monitor hosts with OpenTelemetry](../../solutions/observability/get-started/quickstart-monitor-hosts-with-opentelemetry.md)
54
+
*[Quickstart: Unified Kubernetes Observability with Elastic Distributions of OpenTelemetry (EDOT)](../../solutions/observability/get-started/quickstart-unified-kubernetes-observability-with-elastic-distributions-of-opentelemetry-edot.md)
55
+
*[Quickstart: Collect data with AWS Firehose](../../solutions/observability/get-started/quickstart-collect-data-with-aws-firehose.md)
56
56
57
57
58
58
### Get started with other features [_get_started_with_other_features]
@@ -61,20 +61,20 @@ Want to use {{fleet}} or some other feature not covered in the quickstarts? Foll
61
61
62
62
% Stateful only for Universal profiling
63
63
64
-
*[Get started with system metrics](../../../solutions/observability/infra-and-hosts/get-started-with-system-metrics.md)
65
-
*[Get started with application traces and APM](../../../solutions/observability/apps/fleet-managed-apm-server.md)
66
-
*[Get started with synthetic monitoring](../../../solutions/observability/apps/synthetic-monitoring.md)
67
-
*[Get started with Universal Profiling](../../../solutions/observability/infra-and-hosts/get-started-with-universal-profiling.md)
64
+
*[Get started with system metrics](../../solutions/observability/infra-and-hosts/get-started-with-system-metrics.md)
65
+
*[Get started with application traces and APM](../../solutions/observability/apps/fleet-managed-apm-server.md)
66
+
*[Get started with synthetic monitoring](../../solutions/observability/apps/synthetic-monitoring.md)
67
+
*[Get started with Universal Profiling](../../solutions/observability/infra-and-hosts/get-started-with-universal-profiling.md)
68
68
69
69
70
70
## Additional guides [_additional_guides]
71
71
72
72
Ready to dig into more features of Elastic Observability? See these guides:
73
73
74
-
*[Create an alert](../../../solutions/observability/incident-management/alerting.md)
75
-
*[Create a service-level objective (SLO)](../../../solutions/observability/incident-management/create-an-slo.md)
74
+
*[Create an alert](../../solutions/observability/incident-management/alerting.md)
75
+
*[Create a service-level objective (SLO)](../../solutions/observability/incident-management/create-an-slo.md)
76
76
77
77
## Related content for Elastic Stack v9.0 [_related_content]
78
78
79
79
*[Starting with the {{es}} Platform and its Solutions](/get-started/index.md) for new users
80
-
*[Adding data to {{es}}](../../../manage-data/ingest.md) for other ways to ingest data
80
+
*[Adding data to {{es}}](../../manage-data/ingest.md) for other ways to ingest data
Copy file name to clipboardExpand all lines: solutions/observability/incident-management.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,6 @@ Explore the topics in this section to learn how to respond to incidents detected
10
10
11
11
|||
12
12
| --- | --- |
13
-
|[Alerting](../../../solutions/observability/incident-management/alerting.md)| Trigger alerts when incidents occur, and use built-in connectors to send the alerts to email, slack, or other third-party systems, such as your external incident management application. |
14
-
|[Cases](../../../solutions/observability/incident-management/cases.md)| Collect and share information about {{observability}} issues by opening cases and optionally sending them to your external incident management application. |
15
-
|[Service-level objectives (SLOs)](../../../solutions/observability/incident-management/service-level-objectives-slos.md)| Set clear, measurable targets for your service performance, based on factors like availability, response times, error rates, and other key metrics. |
13
+
|[Alerting](../../solutions/observability/incident-management/alerting.md)| Trigger alerts when incidents occur, and use built-in connectors to send the alerts to email, slack, or other third-party systems, such as your external incident management application. |
14
+
|[Cases](../../solutions/observability/incident-management/cases.md)| Collect and share information about {{observability}} issues by opening cases and optionally sending them to your external incident management application. |
15
+
|[Service-level objectives (SLOs)](../../solutions/observability/incident-management/service-level-objectives-slos.md)| Set clear, measurable targets for your service performance, based on factors like availability, response times, error rates, and other key metrics. |
Copy file name to clipboardExpand all lines: solutions/observability/infra-and-hosts.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,9 +14,9 @@ Explore the topics in this section to learn how to observe and monitor hosts and
14
14
15
15
|||
16
16
| --- | --- |
17
-
|[Analyze infrastructure and host metrics](../../../solutions/observability/infra-and-hosts/analyze-infrastructure-host-metrics.md)| Visualize infrastructure metrics to help diagnose problematic spikes, identify high resource utilization, automatically discover and track pods, and unify your metrics with other observability data. |
18
-
|[Universal Profiling](../../../solutions/observability/infra-and-hosts/universal-profiling.md)| Profile all the code running on a machine, including application code, kernel, and third-party libraries. |
19
-
|[Tutorial: Observe your Kubernetes deployments](../../../solutions/observability/infra-and-hosts/tutorial-observe-kubernetes-deployments.md)| Observe all layers of your application, including the orchestration software itself. |
20
-
|[Tutorial: Observe your nginx instances](../../../solutions/observability/infra-and-hosts/tutorial-observe-nginx-instances.md)| Collect valuable metrics and logs from your nginx instances. |
21
-
|[Troubleshooting](../../../troubleshoot/observability/troubleshooting-infrastructure-monitoring.md)| Troubleshoot common issues on your own or ask for help. |
17
+
|[Analyze infrastructure and host metrics](../../solutions/observability/infra-and-hosts/analyze-infrastructure-host-metrics.md)| Visualize infrastructure metrics to help diagnose problematic spikes, identify high resource utilization, automatically discover and track pods, and unify your metrics with other observability data. |
18
+
|[Universal Profiling](../../solutions/observability/infra-and-hosts/universal-profiling.md)| Profile all the code running on a machine, including application code, kernel, and third-party libraries. |
19
+
|[Tutorial: Observe your Kubernetes deployments](../../solutions/observability/infra-and-hosts/tutorial-observe-kubernetes-deployments.md)| Observe all layers of your application, including the orchestration software itself. |
20
+
|[Tutorial: Observe your nginx instances](../../solutions/observability/infra-and-hosts/tutorial-observe-nginx-instances.md)| Collect valuable metrics and logs from your nginx instances. |
21
+
|[Troubleshooting](../../troubleshoot/observability/troubleshooting-infrastructure-monitoring.md)| Troubleshoot common issues on your own or ask for help. |
22
22
|[Metrics reference](asciidocalypse://docs/docs-content/docs/reference/data-analysis/observability/metrics-reference.md)| Learn about the key metrics displayed in the Infrastructure UI and how they are calculated. |
0 commit comments