The Instrumenter proactively enables telemetry collection from their environment. They’re primarily concerned with observability data before it enters the observability platform. Their primary motivation is to ensure the data is flowing as expected. In their role, The Instrumenter might suffer from the following pain points:Documentation Index
Fetch the complete documentation index at: https://docs.chronosphere.io/llms.txt
Use this file to discover all available pages before exploring further.
- Adding custom metrics to code requires a deep understanding of the service.
- Naive configuration generates too much data volume.
- Manual instrumentation is painful, time-consuming, and can be rendered useless by incompleteness.
- A single system can have many different formats and standards.
- Comprehensive tooling is lacking.
Common tasks
The Instrumenter uses Chronosphere Observability Platform to complete the following tasks common to their role, which helps alleviate their pain points:- Installs and configures collectors to send data to Observability Platform.
- Enables observability data collection in the environment and verifies that metrics and logs arrive correctly.
- Creates patterns and frameworks so other users can send observability data following collector configuration best practices.
- Configures collectors to apply helpful taxonomy so data is recognizable and usable when it enters the platform, using derived labels.
- Configures collectors to reject unnecessary data using drop rules to reduce egress and storage costs.