Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

reclassify a collectd.log entry severity

Description

This seems more like INFO or at worst WARN to me? INFO is ideal as this tends to get spammy with large collections.

2012-07-24 12:01:36,641 ERROR [CollectdScheduler-50 Pool-fiber25] CollectionResourceWrapper: getCounterValue: invalid interval rate for node[4732].interfaceSnmp[Se0_1_0].ifInOctets. The last valid value for the metric was 1.296939446E9 at Tue Jul 24 12:01:35 PDT 2012. This value will be used instead.

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Benjamin Reed July 9, 2013 at 10:49 AM

It was actually already changed to WARN in 1.12, but I think making it a DEBUG is reasonable, if the time is 0, the rate is 0, if people have graph issues, they can turn debug on.

Patrick Tuite July 5, 2013 at 4:49 AM

Is it benign? I've a lot of noise from it in my logs

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

PagerDuty

Created July 24, 2012 at 3:12 PM
Updated January 27, 2017 at 4:20 PM
Resolved July 9, 2013 at 10:49 AM