At its core Nobl9 helps your organization set and understand reliability goals. By tracking the performance of your systems you can ensure balanced and efficient reliability. The platform collects metrics from all of your existing monitoring systems and calculates your performance. SLOs are defined in an expressive SLOs-as-code language to drive automated actions when SLOs are at risk. Nobl9 supports the cross-team workflow of various stakeholders to refine and improve the efficiency and reliability of your service over time.
How NOBL9 Fits Into Your Environment
Whenever you pick a new tool, it’s important that it fits with how you already run things. Nobl9 can be added to many development environments whether on premises or in the cloud. Engineers can create SLO configurations that tell Nobl9 how to interpret raw service level indicators from your existing monitoring system. Nobl9 triggers events to automate your response to reliability issues, whether that’s filing a bug or paging an on-call SRE.
Collect SLI Data From External Monitoring
It’s not about having the most metrics to monitor, it’s about the right metrics that impact your business. Knowing which metrics are impacting customer experience can cut monitoring storage costs by 80% as well as focus your attention on what truly matters in order to signal-boost your monitoring.
Nobl9 collects the key metrics from existing monitoring systems including Datadog, New Relic, Prometheus, Lightstep, and more. These service KPIs (aka service level indicators) can be used to measure and trigger action related to reliability issues across your stack.
Real-time and Historical Reporting
Correlating your reliability goals to signals of business success or failure lets you proactively tackle early warning of increased errors — before an outage erupts. Break down organizational silos with SLOs to bridge the conversation between business and technical stakeholders.
Nobl9 real-time and historical reports show clear data-driven answers to critical questions like, “should we focus on features or technical debt?” and “are we wasting money on excessive cloud resources?” With Nobl9, you can achieve the right balance of speed, safety, and spend by using the shared language of SLOs.
User and Time Period Segmentation
Your users are unique and they expect the best service, but most will forgive minor issues. During critical times — at first sign up or during the holiday shopping season, for example — you want your service to just work. Other periods or tasks are less likely to cause frustration and churn.
Nobl9 allows you to create business rules and define “facets” of users to understand their needs and experience fully. See individuals that are struggling, groups of users from a single location or company, define critical business periods, and codify contractual obligations (SLAs) so your company can focus on delivering the right service across digital interfaces.
GitOps, IaC, CLI/API/GUI
Nobl9 was designed to solve business problems, but crafted for engineers. We’re quite proud of our developer experience, and we’ve gotten great reviews from our users. Use copypasta and pull requests to share SLOs across your engineering team.
Every Nobl9 task has 3 ways to work: CLI, API, and web GUI to suit your context and keep you productive. Nobl9 SLOs are declared with infrastructure-as-code yaml files (that mimics Kubernetes config) that are stored in Git. Because Nobl9 has advanced error-budget based alerting policies, you’ll see fewer false positives (up to 70% than traditional alerts) no matter who is carrying the pager.