Observability Concepts: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 6: | Line 6: | ||
=<span id='Log'></span>Logs= | =<span id='Log'></span>Logs= | ||
=<span id='Metric'></span>Metrics= | =<span id='Metric'></span>Metrics= | ||
{{Internal|Prometheus_Concepts#Metrics|Prometheus Metrics}} | |||
==Aggregated Metrics== | ==Aggregated Metrics== | ||
Not all metrics are stored. | Not all metrics are stored. | ||
==Raw Metrics== | ==Raw Metrics== | ||
All metrics are stored, so individual events can be identified. | All metrics are stored, so individual events can be identified. | ||
=<span id='Trace'></span>Traces= | =<span id='Trace'></span>Traces= | ||
{{Internal|Tracing|Tracing}} | {{Internal|Tracing|Tracing}} | ||
Revision as of 01:39, 6 September 2023
Internal
Overview
Observability is the art of understanding the dynamic state of your systems, service and infrastructure. Observability data consists of metrics, traces, logs, metadata, exceptions and even real-time events. Observability analysis leverages machine learning and heuristic techniques to generate insights from data.
Logs
Metrics
Aggregated Metrics
Not all metrics are stored.
Raw Metrics
All metrics are stored, so individual events can be identified.