This is an IBM Automation portal for Cloud Management and AIOps products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
We think it should be possible to create alerts based on defined SLIs and SLOs. Currently, it's not possible to alert if something is consuming an available error budget too fast over a certain time or that we consumed the error budget already completely. The current SLO implementation is only useful during the SLO review meetings, but we can't define actionable alerts.
Here are some simple examples borrowed from the SRE book:
Alert based on error rate >= SLO threshold
Alert based on burn rate
Multiwindow, Multi-Burn-Rate Alerts
The goal is to identify error budget threats early on and not in an e.g. weekly meeting when it's already too late. That would empower the SLO features Instana offers by a large degree.
Set Alerts on SLO violation or trends on dashboards
I have many SLO dashboards with respect to different Application/Service/Endpoint that in turn is defining one user journey and SLIs related to that. But I have no way to set alert for the trends in SLO observation via dashboard. We tried to do it...
4 months ago
in Instana / Alert
Planned for future release
Do not place IBM confidential, company confidential, or personal information into any field.