Cloud Management and AIOps
Hide about this portal


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.

Add a new idea Subscribe
Status Delivered
Workspace Instana
Categories Agent Logging Tracing
Created by Guest
Created on Jun 12, 2024

RELATED IDEAS

Logs of span rate limiting should be write in INFO level in agent.log to detect it worked.

See this idea on ideas.ibm.com

Instana manual explains as following;

> If you see logs like Suppressed spans due to high number of short or Discarded span due to queue overflow in the agent log, it means that the Java tracer experienced heavy load on span processing.

The description seems not to require user to set DEBUG mode, however it is required actually.
If I set agent.log to Debug mode, I can detect it in the log. However it is not acceptable to set DEBUG mode permanently.

It means users have no way of knowing that span rate limiting has been executed on production environment.

In the last discussion, ENG team said it was difficult to write in INFO log because suppressed messages will be a huge amount. However I disagree with this point. Since the suppressed messages are only output every 10 minutes.

I expect to output it as an INFO level in agent.log.

Idea priority High
  • Guest
    Reply
    |     Aug 22, 2024

    This Aha is opened for Logging category, but if it is not appropriate, please chagne the category to the best one.

  • Guest
    Reply
    |     Aug 21, 2024

    We explain "100% trace" stroy everywhere like bellow (but it is not 100$ in reality). Now this appears IBM's betrayal to the client.

    https://ibm.seismic.com/Link/Content/DCqphTgCPC37MG2BdfVdXfmV2jD8

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.