Skip to Main Content
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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.

Status Submitted
Workspace Instana
Categories Extend Capabilities
Created by Guest
Created on May 12, 2026

Add ability to mark http status codes as errors though they are not in the 5xx range

Hi,

Certain application owners in our organisation have the need to report error rates based on functional errors which are e.g. reported with a 412 (or other) http status codes. This is technically not an error and those requests are not marked as errors or added to the erroneous calls metrics.

Ideally we can add a configuration to the application perspective allowing us to define custom http status that should be treated as errors - mark http status 410-412, 420 as erroneous.

This is for reporting purposes and possibly SLO not for alerting. We can of course create events using smart alerts based on http status codes - in our case we need the error rate metric though.

Thanks and regards,

Rainer

Idea priority High