Logz.io Service Performance Monitoring dashboard (SPM) provides an overview of your systems’ health by aggregating Request, Error, and Duration (R.E.D) metrics from span data. The dashboard helps you to pinpoint and isolate incidents in your system quickly.
The following guide helps you configure the OpenTelemetry collector to extract metrics from spans generated from your application instrumentation, and send them to Logz.io.
Once configured and deployed, the collector accepts the spans and processes them through two pipelines:
The first pipeline sends the spans to the Logz.io backend, where you can analyze single traces and focus on slowness and bottlenecks.
The second pipeline extracts the metrics from the same spans, aggregates them, and sends them to Logz.io’s Prometheus-based account.
- Activate the Service Performance Monitoring dashboard
- Configure and ship your data
- Check Logz.io for your metrics
Activate the Service Performance Monitoring dashboard
Only account admins can activate the Service Performance Monitoring dashboard.
To get started with Service Performance Monitoring, navigate to Tracing, switch to the Monitor tab located at the top of the screen, and click on the Start now button.
You’ll then be given a heads up that SPM requires an active Metrics plan. If you don’t have an active Metrics plan, a trial account will be automatically created for you, free of charge.
The Metrics account trial will be available for 2 weeks. Afterward, you’ll need to purchase a Metrics plan to continue using your Service Performance Monitoring dashboard.
If you have an active Metrics plan, the Service Performance Monitoring dashboard will try to allocate data from your existing plan. To run, you need between 1,000-5,000 UTS in your Metric plan that are not assigned to any account.
Once setup is complete, you can change and re-adjust your data allocation by navigating to the Manage accounts page.
If you don’t have enough UTS available in your existing Metrics account, you’ll need to re-allocate or purchase additional UTS to your account.
Logz.io sub account users
You can only activate Service Performance Monitoring from your main Logz.io account.
If you want to add Service Performance Monitoring to a Tracing account that’s only visible from a sub account, you’ll need first to add visibility to the main account.
For example, Sock Shop-Tracing DEV is only visible from the sub account Sock Shop DEV:
In this case, you only have visibility to Sock Shop-Tracing DEV from the sub account Sock Shop DEV, and you won’t be able to activate Service Performance Monitoring for this Tracing account.
To enable Service Performance Monitoring, you’ll need to add Sock Shop (the main account) to the list of authorized accounts.
After adding the main Sock Shop account to the list inside your Sock Shop-Tracing DEV settings, you’ll have access to the Sock Shop-Tracing DEV account from the main Sock Shop account, and you’ll be able to go through the activation process.
This process is only required for the duration of the activation process. Once activation is complete, you can restore your original account settings and remove Sock Shop from the list of authorized accounts.
Configure and ship your data
You’ll need to configure your collector to extract metrics from your data. Log into your Logz.io account and follow these steps to modify the OpenTelemetry collector.
You can configure the collector to ship data from a Local host, Docker, or Kubernetes.
Before deploying, make sure the collector you’re using is version v0.44.0 and up.
Once everything is set, restart the collector to apply the configuration changes.
Check Logz.io for your metrics
Give your metrics some time to reach and render from your system to Logz.io, then navigate to Tracing > Monitor to view the aggregated metrics for your services and operations.