Cloud Management and AIOps
This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation 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 updates on 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
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Hi, thank you for submitting this idea.
It is possible to achieve this creating a Correction Window and applying it to the SLO you've created. Correction Windows are typically used when there is maintenance planned in the future and any reduction in Service Level should not be counted against the error budget during that window. (It can also be made to apply retrospectively so isn't quite the same as Instana maintenance windows). See this page in the documentation: https://www.ibm.com/docs/en/instana-observability/1.0.309?topic=slos-slo-correction-windows
So you would create an SLO to monitor for login failures over the course of a day / week / month etc or a rolling SLO. Then you would create a Correction Window to exclude 10 hours from 10pm.
If you have an SLO that is event based and you define the bad events as being HTTP 401 responses and good events as being all other responses, to the login page, then all events, good and bad, during the Correction Window will be ignored for the purposes of error budget.