Skip to:

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

Thresholding on WSMan datasources appears broken

Description

Thresholding on wsman resources appears to get confused about which instance is which, causing thresholds to flap or reset each other when processing thresholds for different datasources, e.g.

ResourceType

collection group

Threshold group

Datacollection happens as expected, jrbs are populated and graphs work as expected. Thresholds never fire, or fire and immediately rearm when processing the next datasource.

Not sure what else to check. No other datacollection mechanisms (jdbc, snmp, etc) exhibit this behavior.

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Jesse White June 1, 2017 at 12:09 PM

Jesse White June 1, 2017 at 9:48 AM

Awesome. Thanks for helping us work through this.

Dino Yancey June 1, 2017 at 9:45 AM

Once 1e937ff66ca661091c6344142f8bd2ac64ebcb58, 803ec9e84fe8b145a4d468d2966181cdfb7a03cd, and cdcb7bafaf23e7ec0ccd6ca034f537851424ce53 are applied, thresholds appear to process normally for these resources. Thanks!

Jesse White May 30, 2017 at 5:34 PM

True, both of those resources were affecting the same "threshold state".

This should be fixed with: cdcb7bafaf23e7ec0ccd6ca034f537851424ce53

Dino Yancey May 30, 2017 at 3:24 PM

Yes, but those are two different instances (I: and HarddiskVolume16) processed in the same thresholding pass, in the same second. If it were resetting due to normal circumstance that would represent ~2.6 terabytes becoming free in about 1ms So it's really the same behavior as before, but the instance names are correct in the debug output now.

Fixed

Details

Assignee

Reporter

Components

Sprint

Fix versions

Affects versions

Priority

PagerDuty

Created May 18, 2017 at 5:52 PM
Updated June 6, 2017 at 7:08 PM
Resolved June 5, 2017 at 12:29 PM