Issues
- Node level menu option to turn on/off debug level logging of collected and pollerd for nodeNMS-11886
- Add information to the WEB GUI in the building rules area for notificationsNMS-11798Resolved issue: NMS-11798Bonnie Robinson
- The Dev Documentation doesn't have information about the Hardware InventoryNMS-11730Resolved issue: NMS-11730Mark Mahacek
- Failed to run Jasper report local_Serial-Interface-Utilization-Summary: Key receive rate is duplicated in pie datasetNMS-9875Resolved issue: NMS-9875Christian Pape
- Add a command-line tool to create a thread dumpNMS-9872Resolved issue: NMS-9872Jeff Gehlbach
- Copyright dates need a bump for 2018NMS-9871Resolved issue: NMS-9871Jeff Gehlbach
- It is not possible to see Statsd results on the WebUINMS-9861Resolved issue: NMS-9861Chandra Gorantla
- Enlinkd startup fails due to NPE in BroadcastDomain classNMS-9852Resolved issue: NMS-9852Christian Pape
- filters for hardware inventoryNMS-9844
- Documentation typo for /rest/ifservices on the developers guideNMS-9842Resolved issue: NMS-9842Alejandro Galue
- bsmd: avoid processing alarm lifecycle events when no rules are definedNMS-9835Resolved issue: NMS-9835Jesse White
- ES REST plugin not doing preemptive basic authNMS-9699Resolved issue: NMS-9699Jesse White
- Asset data export / import is practically unusableNMS-6858
13 of 13
Node level menu option to turn on/off debug level logging of collected and pollerd for node
Description
Acceptance / Success Criteria
None
Attachments
2
Lucidchart Diagrams
Details
Assignee
UnassignedUnassignedReporter
John BlakeJohn BlakeAffects versions
Priority
Minor
Details
Details
Assignee
Unassigned
UnassignedReporter
John Blake
John Blake
Affects versions
Priority
MinorPagerDuty
PagerDuty
PagerDuty
Created October 1, 2018 at 8:16 PM
Updated June 4, 2019 at 8:10 AM
Activity
Show:
John BlakeOctober 1, 2018 at 8:27 PM
I've attached 2 scripts that will output the configuration syntax to add to log4j2.xml to log a specific node.
John BlakeOctober 1, 2018 at 8:24 PM
The specific logging can be done only on pollerd and collectd since those are currently the only 2 that have Contexts available.
Basically, a new "logger" and a new "appender" are added to log42j.xml and use a filter to identify the specific node (node label, IP, etc).
2 items in confluence for explanation
https://confluence.internal.opennms.com/pages/viewpage.action?pageId=18153483
https://confluence.internal.opennms.com/display/SUP/Create+a+log+from+collected+data+for+a+specific+IP+in+log4j2.xml
B
Currently, we have to enable collected at DEBUG level for all devices by default. then grab thru the collectd logs to try and find the node we are troubleshooting. This is not feasible if there are lots of devices. It would be great to be able to enable debug level logging of a specific node from its node page. The output would go to a separate set of logs instead of the default collected.log.
This can be manually done with log4j2.xml by editing the xml file, but a menu option for it would be preferred.