Support Migration Notice: To update migrated JIRA cases click here to open a new case use www.vmware.com/go/sr | vFabric Hyperic 5.7.0 is Now Available

Hyperic HQ

Add CommandListener to agent's disable overly verbose logging section by default

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Deferred
  • Affects Version/s: 4.6.5
  • Fix Version/s: None
  • Component/s: Agent / PDK
  • Case Links:
    none
  • Regression:
    No

Description

Support and customers are complaining about the new logging in 4.6.5 being overly verbose. Main cause appears to be org.hyperic.hq.agent.server.CommandListener logging it's expected accept timeout every 2 seconds. This makes debugging issues impossible by default. This issue is being logged under the improvement of supportability.

The following patch will disable this logging by default when "agent.logLevel=DEBUG" is set

diff --git a/dist/hyperic-hq-agent/src/main/resources/conf/agent.properties b/dist/hyperic-hq-agent/src/main/resources/conf/agent.properties
index cc3ead1..4315aaf 100644
--- a/dist/hyperic-hq-agent/src/main/resources/conf/agent.properties
+++ b/dist/hyperic-hq-agent/src/main/resources/conf/agent.properties
@@ -131,6 +131,7 @@ log4j.logger.org.hyperic.hq.agent.server.AgentDListProvider=INFO
 log4j.logger.org.hyperic.hq.agent.server.MeasurementSchedule=INFO
 log4j.logger.org.hyperic.util.units=INFO
 log4j.logger.org.hyperic.hq.product.pluginxml=INFO
+log4j.logger.org.hyperic.hq.agent.server.CommandListener=INFO
 
 # Only log errors from naming context
 log4j.category.org.jnp.interfaces.NamingContext=ERROR

Activity

Hide
Scott Feldstein added a comment -

changing to major as there is a workaround to the issue.

Show
Scott Feldstein added a comment - changing to major as there is a workaround to the issue.
Hide
Yoav Epelman added a comment -

Bulk change to new components

Show
Yoav Epelman added a comment - Bulk change to new components
Hide
Idan Hod added a comment -

As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology.

Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix.

We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base.

This bug has been deferred as part of the new policy.

We appreciate your cooperation and continues contribution to the improvement of Hyperic.

Show
Idan Hod added a comment - As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology. Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix. We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base. This bug has been deferred as part of the new policy. We appreciate your cooperation and continues contribution to the improvement of Hyperic.

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    40 weeks, 4 days ago