Issues
- Add debug logging to SNMP Property Extenders on match failureNMS-15743Resolved issue: NMS-15743Christian Pape
- Stop packaging activemq-web-console.warNMS-15686Resolved issue: NMS-15686Benjamin Reed
- send-events-to-elasticsearch karaf command passes username/password in reverseNMS-15638Resolved issue: NMS-15638Mark Mahacek
- Docs section about startup configuration and opennms.confNMS-15634Resolved issue: NMS-15634Bonnie Robinson
- update to latest groovy 2.xNMS-15633Resolved issue: NMS-15633Benjamin Reed
- Syslog Northbounder maxMessageSize config option is not usedNMS-15606Resolved issue: NMS-15606Alex May
6 of 6
Add debug logging to SNMP Property Extenders on match failure
Fixed
Description
Acceptance / Success Criteria
None
Details
Assignee
Christian PapeChristian PapeReporter
Mark MahacekMark MahacekHB Grooming Date
Jun 21, 2023HB Backlog Status
Refined BacklogSprint
NoneAffects versions
Priority
Medium
Details
Details
Assignee
Christian Pape
Christian Pape
Reporter
Mark Mahacek
Mark Mahacek
HB Grooming Date
Jun 21, 2023
HB Backlog Status
Refined Backlog
Sprint
None
Affects versions
Priority
Medium
PagerDuty
PagerDuty
PagerDuty
Created June 9, 2023 at 3:43 PM
Updated December 21, 2023 at 3:10 PM
Resolved December 21, 2023 at 6:56 AM
Activity
Show:
Christian PapeDecember 21, 2023 at 6:56 AM
Merged.
Christian PapeDecember 20, 2023 at 2:57 PM
Now it is
Mark MahacekDecember 20, 2023 at 2:56 PM
That PR isn’t related to this NMS issue.
Christian PapeDecember 20, 2023 at 1:57 PMEdited
Please review:
* PR:
There is no logging for when property extenders don’t match, which makes it harder to troubleshoot new configurations. Proposal is to add a debug message to each extender if there is no match.