Skip to Main Content
Cloud Management and AIOps

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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace Instana
Categories Alert
Created by Guest
Created on Jul 24, 2023

Allow to alert only on new, unique errors

For front-end browser errors in particular, it would be very helpful to receive alerts for new errors, which are unique based on their error message and source code position.

Instana already contains the concept of unique JavaScript errors based on error message and source code position. I would hope that browser-specific variations for the error message are already taken into account to bundle errors across browsers and that the source code position has some flexibility when it comes to changes to the source code in the vicinity of the code for which the error occurred.

Idea priority High
  • Guest
    Sep 11, 2023

    Hi Dania,

    • Do you need to be notified the first time a new error is observed?

    Yes, that is my suggestion for this new alert.

    • Even if the error appears in just 1 user session?

    It would be helpful, maybe in a second step, to allow to add a filter to it like: new error & at least x user sessions were affected within timeframe y.

    • Why is so important for you to know if javascript error were introduced?

    This information is crucial for us, as it can help identify a recent deployment that contained a new bug. We are actually already spending a lot of time trying to determine manually if an error we were alerted about was new and it's becoming unmanageable.

    The main problem with the current alerting is that the threshold is not calculated for individual errors, but for any JS error occurring. As our code base is quite large with multiple teams working on it and a good number of errors have not been resolved or have been classified as not important enough to be resolved yet, the error threshold is to easily reached if we keep it too low. That makes it very difficult to identify (new) bugs that only occur a few times within the timeframe of the alert.

    This new alert would only work well if the identification of uniqueness is reliable and if this wouldn't lead to too many know errors being alerted as new due to unrelated source code change.

    Just to point out that this is a feature that Sentry offers and that it's even the default alerting: So it seems to makes sense to others too.


  • Admin
    Dania Grave de Peralta Reyes
    Sep 8, 2023

    Hello Rene,

    I would like to better understand your idea.

    • Do you need to be notified the first time a new error is observed?

    • Even if the error appears in just 1 user session?

    • Why is so important for you to know if javascript error were introduced?