Skip to:

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

Design thresholding support for telemetryd on Sentinel

Description

Related to https://opennms.atlassian.net/browse/HZN-1526#icft=HZN-1526, we should support thresholding in telemetryd when running on Sentinel.

Given the distributed nature of Sentinel there are additional considerations that need to be made: Is it possible to reliably route the metrics for a given resource to the same Sentinel? If not then how we do track the thresholding state and share this across Sentinels?

Success criteria:

  • We can trigger thresholds for metrics persisted by telemetryd on Sentinel

 

Acceptance / Success Criteria

None
100% Done
0

Lucidchart Diagrams

Activity

Jesse White July 3, 2019 at 5:56 PM

With https://opennms.atlassian.net/browse/NMS-12081#icft=NMS-12081 we have moved thresholding out of the opennms-services module and introduced a new ThresholdingService interface which can be used to apply thresholding to any CollectionSet.

In https://opennms.atlassian.net/browse/NMS-11797#icft=NMS-11797 telemetryd will be updated to use this new service, allowing us to apply thresholding to streaming telemetry.

The next challenges arise from processing streaming telemetry on Sentinel. https://opennms.atlassian.net/browse/NMS-12140#icft=NMS-12140 (config), https://opennms.atlassian.net/browse/NMS-12141#icft=NMS-12141 (events), https://opennms.atlassian.net/browse/NMS-12142#icft=NMS-12142 (stickiness) and https://opennms.atlassian.net/browse/NMS-12143#icft=NMS-12143 (state) should provide the building blocks necessary for making this work.

Jesse White April 12, 2019 at 4:04 PM
Edited

We also need to solve the problem of sharing the thresholding configuration with the core and the Sentinels. This could be an opportunity to move this to the database, or we could find a more generic solution that works with our configuration files as-is.
 

Fixed

Details

Assignee

Reporter

Sprint

Fix versions

Priority

Parent

PagerDuty

Created April 11, 2019 at 3:59 PM
Updated July 3, 2019 at 5:56 PM
Resolved July 3, 2019 at 5:56 PM

Flag notifications