snmpCollect being reset to C even if a policy sets it to N

Description

I think we need to fix this portion of the code to not reset snmpCollect=C if it is already set to N when merging snmp properties.

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Alex May January 5, 2023 at 1:16 PM

I don’t think there’s a way to reset UC/UN once it is set short of manually updating the database. I just created a ticket to track this, see

JianYet December 28, 2022 at 3:26 PM
Edited

say if I had UC or UN set for some SNMP interfaces, later on I changed my mind and decided to use policy instead to manage collection. How do I get out of UC/UN and get to PC/PN? If I understand correctly, nothing overrides UC/UN? Is there a way to reset UC/UN back to C/N besides updating the snmpcollect field manually in the database?

Alex May August 10, 2022 at 12:29 PM

Jeff Gehlbach August 2, 2022 at 3:36 PM

We will move ahead with the 'PN' / 'PC' suggestion from .

Mark Mahacek August 1, 2022 at 3:59 PM

In that case, the policy would only apply once and then wouldn't be able to change it back if another policy was later introduced to change it back to collect.  

What about a 'PN'/'PC' for policy-set values?

If the value is UC/UN, the policy won't apply.
If the value is PC/PN, policies can update the field, but provisiond's logic can't update the filed.
If the value is C/N, provisiond can apply it's logic to determine collection, and policies can update it to PC/PN when applicable.

Fixed

Details

Assignee

Reporter

HB Grooming Date

HB Backlog Status

Sprint

Fix versions

Affects versions

Priority

PagerDuty

Created July 28, 2022 at 5:01 PM
Updated August 8, 2023 at 2:26 PM
Resolved August 12, 2022 at 2:29 PM