Template built by
Telegraf Plugins used:
- 1 Dashboard:
- 1 bucket:
If you have your InfluxDB credentials configured in the CLI, you can install this template with:
Cribl LogStream Monitoring Dashboard
Many organizations agree that migrating workloads to the cloud or to a newer version of existing tooling can result in cost savings and flexibility. A well-designed observability pipeline is often the key to a quick and painless transition, leading to positive impacts on cost optimization, data visibility, and performance. Cribl’s LogStream product helps teams implement such an observability pipeline by parsing, restructuring and enriching data in flight.
Why monitor Cribl LogStream?
Cribl LogStream collects metrics about itself and can easily send the data to a centralized InfluxDB deployment. This is important to help you maintain availability and performance of your Cribl Logstream as it works to collect and enrich your important streams of data into your applications.
How to use the Cribl LogStream Monitoring Template
Once your InfluxDB credentials have been properly configured in the CLI, you can install the Crible LoSstream template using the Quick Install command. Once installed, log Into your Cribl LogStream master node and configure your InfluxDB Destination:
Set environment variables for the InfluxDB Destination:
Write API URL- Your InfluxDB Cloud Endpoint, here's an example:
Database Name- Your InfluxDB Name:
Extra HTTP Headers- Navigate to Advanced Settings and add the
AuthorizationHeader with your
Tokenas the value.
To start sending Cribl metrics with the template-provided configuration, you need to set up the following: Click on Sources and select the Cribl Internal Icon. Once installed, you'll need to set up Cribl LogStream to send the internal metrics to your InfluxDB deployment. Check out the Cribl LogStream docs on how to send your Cribl Internal metrics to the InfluxDB destination.
Key Cribl LogStream Monitoring metrics to monitor
Some of the most important Cribl Logstream monitoring metrics that you should proactively monitor include:
- Events (in/out)
- Bytes (in/out)
- Event Sources
- Event Destinations