Track SLOs based on your monitoring data

Create reports and notify teams when performance issues arise.

Contact
Integrates with metrics APIs from popular observability tools:

What are SLOs?

Service Level Objectives (SLOs) are the established method to track system performance in SRE and DevOps organizations. Each SLO defines a target value for an SLI (Service Level Indicator, a defined metric). For example, a performance SLO for a web application might state that 99% of requests must be answered in less than 500 ms each hour. Each hour in which the objective is not met counts against a defined "error budget". When the error budget has been depleted, actions need to be taken to improve performance and get back into SLO compliance.

SLOs can be difficult to manage when many metrics across different sources of monitoring data are involved.

Monitoring SLOs with Metralyze

  1. Connect your monitoring data sources
    Metralyze connects to your monitoring system's API to retrieve operational metrics on your systems.
  2. Configure SLO watchers
    Setup watchers to retrieve the metrics needed to calculate SLOs. Metralyze fetches aggregated data from your monitoring system based on filter conditions that you specify for each SLO. Define thresholds or trends to watch for, and notification rules.
  3. Receive event notifications when SLOs are in danger
    Metralyze supports sending events to Slack and Zapier. Alert teams on SLO and error budget issues by automatically posting messages on Slack. Send events to Zapier to trigger automated actions, such as creating JIRA tickets.
  4. View SLO reports
    Each watcher generates a trail of data that shows time periods in which SLOs were or were not met. Generate time-based reports on SLOs using this data.

Metralyze connects with your tools

Use time-series data from your favorite tools to feed SLO watchers and reports.

Frequently Asked Questions

What do I need to start collecting data from my tools?

For each tool you want to access through the Metralyze API, you need an account or API token in that tool. For example, for Instana you will need to create an API token.

01

Can Metralyze configuration be automated?

All configuration in Metralyze is available via API. That means that watchers, SLO definitions and connections be managed from within CI/CD pipelines.

02

How can a common API work across different tools?

Metralyze focuses only on time-series data, which is characterized by having a set of time-stamped metrics together with a number of dimensions that give context for those metrics. Many monitoring and analytics tools offer the same kind of data. What we do is to offer a common query API and data format that works across all tools that we integrate with.

03

Can I use Metralyze?

Metralyze is exclusively licensed to a retail e-commerce company by Proscaler GmbH. Contact us to discuss solutions for similar use cases.

04