Meters
Automated metrics monitor for Joule pipelines: data pipelines, processors, transport, storage
Last updated
Automated metrics monitor for Joule pipelines: data pipelines, processors, transport, storage
Last updated
This page describes the automatic monitoring metrics available for different components within the Joule system, focusing on:
Data pipelines
Processors
Transport
Storage
Each component has specific metrics enabled by default, allowing users to monitor performance and resource usage effectively.
This monitor tracks the flow of events through the processing pipeline, providing insight into the volume of events processed. It helps ensure that events are moving through the pipeline efficiently and without delays.
Queued
Number of events queued for processing
Processed
Number of events successfully processed
Failed
Number of failed events not processed by the consuming / publishing transport
Every processor has a set of metrics turned on by default. If a processor is assigned a symbolic name in the DSL configuration, a bean is created with that name for easier identification and monitoring.
Received
Number of events received by the processor before being queued
Queued
Number of events queued ready for processing
Processed
Number of events successfully processed
Discarded
Number of events discarded, dropped, from the processor which is removed from the processing pipeline
Ignored
Number of events ignored but not dropped from the processing pipeline
Failed
Number of failed events due to a processing failure
Every transport has these metrics turned on by default. If a symbolic name is provided in the DSL configuration, a corresponding bean is created, allowing users to monitor each transport component distinctly.
Queued
Number of events queued ready for processing
Processed
Number of events successfully processed
Failed
Number of failed events not processed by the consuming / publishing transport
This set of metrics helps monitor the I/O (input/output) load on connected data storage systems, providing insights into storage performance and resource usage. Like other components, a symbolic name in the DSL configuration will create a bean for easier monitoring.
Reads
Number of reads performed on the store
Writes
Number of writes performed against the store