As an Asserts customer, all you need to do is connect your Observability Datasources like Prometheus, Cloudwatch et al. to Asserts and then let Asserts apply its intelligence to present root cause insights.
Connect your existing Observability Datasources
Asserts taps into your telemetry data sources like Prometheus, CloudWatch et al., automatically builds a graph of your application and infrastructure components, and indexes the graph for search.
Asserts curates knowledge of common runtime failure patterns and potential causes, so your team doesn’t have to research and maintain these PromQL complex recording and alerting rules for frameworks.
It continuously tracks resource Saturations, Amends (i.e. Changes such as new conatiner deployments, config upgrades, kafka rebalances, scale events et al.), request rate, error rate & latency Anomalies, systemic Failures, and Errors on your golden signals and health metrics.
With our unified search, you can combine components, relations, configurations, and associated assertions to express your intent in an easy natural language expression.
The SRE book recommends Alerting on Service Level Objectives (SLO), to track
"what's broken"and with Asserts setting up your SLOs and tracking your error budget is a breeze. And then finding "why it's broken" is just a click away in our RCA workbench. see more
With our always-on Checks (aka Assertions), you don’t have to wait for SLOs to breach and Alerts to fire. Top Insights presents a stack-ranked view of Services / Nodes that need attention based on their
severity score. And then
Open in Workbenchto find the root cause. see more
In our assertion workbench, dig in to view all the possible causes correlated across time and dependency, with just the right metrics, logs and traces at your fingertip.
e.g., an amend (new deployment) on
api-servertriggered a spike in error rate on an endpoint
/slo/incidents. Jump to
View Logsto see contextual logs in your existing log store, like Kibana, Graylog, et al. see more