Skip to:

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

Attempting to reference attribs collected from more than one WS-Man group of the same resource type in a threshold/expression fails with "can't find attribute"

Description

Microsoft stores a logical disk's type in a class separate from the performance statistics. Using WMI we are able to collect the statistics from one class and the type from another utilizing the same resource type and are then able to use the type in the resource filter of a threshold/expression, but attempting to do so with WS-Man fails with the following error:

See attached for configs. Using Horizon 26.2.2-1. Related support issue is #655.

Acceptance / Success Criteria

None

Attachments

3

Lucidchart Diagrams

Activity

Show:

Christian Pape July 2, 2021 at 3:54 PM

Closing this one since the observed log messages are normal and the behavior is as expected.

Christian Pape July 2, 2021 at 3:52 PM

We have checked the behavior in detail and found that the thresholds are evaluated twice, once for each group. Of course the percentage free space can only be found in one of these groups. So, the observed error message is fine. The threshold filter and the threshold itself works as expected and also the notifications are triggered correctly. We also checked back with the customers and he confirmed that all the thresholds work as expected.

Dino Yancey June 30, 2021 at 10:46 PM
Edited

After several hours of testing, I have:

  • one H28 instance upgraded from 27 where this works

  • one H27 instance where it doesn't work

  • one H28 instance upgraded from that H27 that doesn't work

  • one H28 instance, freshly installed, where this doesn't work

  • one Meridian 2021 instance where it doesn't work

 

`storeByGroup` doesn't seem to have an effect.  I can't find any commonality.  In the logs, I can see it properly check the filter, pass it, and check the threshold against the ds value in exactly one environment, and I'm struggling to reproduce a working state in a fresh environment.

Dino Yancey June 30, 2021 at 1:31 PM

In my test environment, there are wrmLDType (string) and wrmLDTypeG (gauge) and neither work If you're not able to repro this, please show your work because it doesn't function as expected for either myself or the customer.

 

Christian Pape June 30, 2021 at 8:23 AM
Edited

I’m still not able to reproduce the error for my VM even with storeByGroup enabled. As far as I understand, the two files winrm-ld-type.jrb and winrm-ld-type.meta should not exist. They should only exist in the case that wrmLDType is configured as a Gauge, right? So, are these files leftovers? Could you try to delete them and restart OpenNMS? Also, can you display the contents of ds.properties for me.

Cannot Reproduce

Details

Assignee

Reporter

Labels

HB Grooming Date

HB Backlog Status

FD#

Doc Backlog Status

Doc Backlog Grooming Date

Components

Sprint

Priority

PagerDuty

Created June 21, 2021 at 4:55 PM
Updated November 11, 2021 at 8:38 PM
Resolved July 2, 2021 at 3:54 PM