Skip to Main Content
Cloud Platform


This is an IBM Automation portal for Cloud Platform 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
Created by Guest
Created on Apr 30, 2026

Enable Logging Throttling within Quarkus as a documented option similar to OpenLiberty

This business case argues for the value of implementing excessive logging with throttling as a control mechanism, highlighting the benefits of improved visibility, enhanced security, and optimized resource management, ultimately leading to cost savings and greater business efficiency.

1. Enhanced Visibility and Troubleshooting:

Excessive logging, when managed effectively, provides a granular view of system operations. This detailed record-keeping allows for more efficient troubleshooting when issues arise. By having comprehensive logs, development and operations teams can quickly pinpoint the root cause of problems, reducing downtime and accelerating resolution times. This increased observability leads to faster issue resolution, which translates to lower operational costs. For instance, if an application is performing slowly or crashing, logs can provide the precise context and sequence of events leading up to the failure, enabling rapid root cause analysis.

2. Improved Security Posture:

Detailed logs are critical for security monitoring and incident response. By capturing a wide range of events, businesses can more effectively detect and respond to security threats, such as unauthorized access attempts or anomalous behavior. Logs can serve as an audit trail, helping to prove compliance with regulatory standards like HIPAA, PCI DSS, and GDPR. Furthermore, analyzing logs can reveal security vulnerabilities and gaps, allowing proactive measures to be taken to strengthen defenses. In the event of a security breach, comprehensive logs are invaluable for reconstructing the incident, identifying the extent of the damage, and preventing future occurrences.

3. Cost Optimization through Throttling:

While "excessive" logging might intuitively suggest higher costs, the strategic implementation of throttling transforms this into a cost-saving measure. Throttling controls the volume of log data ingested, preventing it from overwhelming systems and incurring unnecessary storage and processing expenses. By setting thresholds, businesses can automatically drop or limit log messages when they reach a predefined limit. This "hard limit" prevents runaway logging during high-activity periods, ensuring that costs remain predictable even during system failures or surges in traffic. Throttling ensures that only essential information is retained, avoiding the expense of storing redundant or low-value data. This selective retention, coupled with potential log compression and tiered storage, can lead to significant reductions in storage and management costs.

4. Operational Efficiency and Resource Management:

By providing deep insights into system performance and user behavior, logs can inform business decisions and optimize resource allocation. Analyzing operational logs helps identify bottlenecks in business processes, allowing for proactive issue resolution and optimization of system configurations. This improved operational efficiency can lead to better resource utilization, minimizing unnecessary downtime and associated costs. For example, understanding how customers use a product through log data can help businesses refine their offerings, potentially increasing revenue.

5. Regulatory Compliance:

Many industries are subject to strict regulations that mandate detailed logging for auditing purposes. Comprehensive logging, combined with effective log management, ensures that businesses can demonstrate adherence to these standards. This proactive approach to compliance helps mitigate the risk of costly fines and reputational damage. Audit logs specifically provide an unalterable historical record of business activities, crucial for policy enforcement and legal proceedings.

Conclusion:

Implementing excessive logging with throttling is not about simply generating more data; it's about strategic data management. This approach provides unparalleled visibility for troubleshooting and security, while throttling ensures that the generated data is managed efficiently and cost-effectively. The combination leads to reduced operational costs, enhanced security, better compliance, and ultimately, a more agile and resilient business. By balancing the need for comprehensive data with cost controls, businesses can leverage logging as a powerful tool for both operational excellence and strategic advantage.

Idea priority Low