이 페이지는 아직 한국어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우
언제든지 연락주시기 바랍니다.Overview
This document lists some of the metrics available from Observability Pipelines. You can:
- Create your own dashboards, notebooks, and monitors with these metrics.
- Use Metrics Summary to see metadata and tags available for the metrics. You can also see which dashboards, notebooks, monitors, and SLOs are using those metrics.
See Getting Started with Tags for more information on how to use tags to group metrics by specific pipelines, Workers, and components.
Estimated usage metric
- Observability Pipelines ingested bytes
- Metric:
datadog.estimated_usage.observability_pipelines.ingested_bytes - Description: The volume of data ingested by Observability Pipelines. See Estimated Usage Metrics for more information.
Host metrics
- Uptime
- Metrics:
pipelines.host.uptime - Description: The amount of time since the host was started, in seconds.
- Bytes in
- Metrics:
pipelines.host.network_receive_bytes_total - Description: The number of bytes received by the host on all interfaces. Use the
device tag to filter per interface, for example device:eth0. - Bytes out
- Metrics:
pipelines.host.network_transmit_bytes_total - Description: The number of bytes sent by the host on all interfaces. Use the
device tag to filter per interface.
Process metrics
- Uptime
- Metrics:
pipelines.uptime_seconds - Description: The amount of time since the Worker process was started, in seconds.
- CPU usage
- Metrics:
pipelines.cpu_usage_seconds_total - Description: The amount of CPU time consumed by the Worker process in seconds (in the user and system space). The rate per second of that metric shows the proportion of the CPU used by the Worker.
- Memory usage
- Metrics:
pipelines.resident_memory_used_bytes - Description: The amount of RSS memory used by the Worker process in bytes.
Component metrics
These metrics are available for sources, processors, and destinations.
- Events in
- Metric:
pipelines.component_received_events_total - Description: The number of events received by the component.
- Available for: Sources, processors, and destinations.
- Events out
- Metric:
pipelines.component_sent_events_total - Description: The number of events the component sends downstream.
- Available for: Sources, processors, and destinations.
- Event bytes in
- Metric:
pipelines.component_received_event_bytes_total - Description: The byte size of events received by the component.
- Available for: Sources, processors, and destinations.
- Event bytes out
- Metric:
pipelines.component_sent_event_bytes_total - Description: The byte size of events the component sends downstream.
- Available for: Sources, processors, and destinations.
- Errors
- Metric:
pipelines.component_errors_total - Description: The number of errors encountered by the component.
- Available for: Sources, processors, and destinations.
- Data dropped intentionally or unintentionally
- Metric:
pipelines.component_discarded_events_total - Description: The number of events dropped. Note: To break down this metric, use the
intentional:true tag to filter for events that are intentionally dropped or the intentional:false tag for events that are not intentionally dropped. - Available for: Sources, processors, and destinations.
- Timed out events
- Metric:
pipelines.component_timed_out_events_total - Description: The number of events that waited more than 5 seconds to be sent to the first processor and resulted in a HTTP 503 error. This could happen when delivery of events are blocked.
- Available for: HTTP-based sources that have a configured timeout, such as the Datadog Agent.
- Timed out requests
- Metric:
pipelines.component_timed_out_requests_total - Description: The number of requests that timed out for sources that send events to the Worker in batches using HTTP requests.
- Available for: HTTP-based sources that have a configured timeout, such as the Datadog Agent.
- Utilization
- Metric:
pipelines.utilization - Description: The component’s activity. A value of
0 indicates an idle component that is waiting for input. A value of 1 indicates a component that is never idle, which means that the component is likely a bottleneck in the processing topology that is creating backpressure, which might cause events to be dropped. - Available for: Processors and destinations.
Buffer metrics (when buffering is enabled)
Track buffer behavior with these metrics:
pipelines.buffer_size_events- Number of events currently in the buffer.
pipelines.buffer_size_bytes- Number of bytes currently in the buffer.
pipelines.buffer_received_events_total- Cumulative number of events written to the buffer.
pipelines.buffer_received_event_bytes_total- Cumulative number of bytes written to the buffer.
pipelines.buffer_sent_events_total- Cumulative number of events read from the buffer and sent downstream.
pipelines.buffer_sent_event_bytes_total- Cumulative number of bytes read from the buffer and sent downstream.
pipelines.buffer_discarded_events_total- Cumulative number of events dropped by a buffer.
pipelines.source_buffer_utilization- Histogram of event count in a source’s buffer. Sources ingest events, then write them to this buffer.
pipelines.source_buffer_utilization_level- Current event count in a source’s buffer. Sources ingest events, then write them to this buffer.
pipelines.source_buffer_utilization_mean- The exponentially weighted moving average (EWMA) of the number of events in the source’s buffer.
pipelines.source_buffer_max_size_events- A source’s maximum buffer size, defined as the number of events.
pipelines.transform_buffer_utilization- Histogram of event count in a processor’s buffer. Processors pull from this buffer, transform the event, and then send it downstream.
pipelines.transform_buffer_utilization_level- Current event count in a processor’s buffer. Processors pull from this buffer, transform the event, and then send it downstream.
pipelines.transform_buffer_utilization_mean- The exponentially weighted moving average (EWMA) of the number of events in the processor’s buffer.
pipelines.transform_buffer_max_size_events- A processor’s maximum buffer size, defined as the number of events.
Further reading
