Details
Assignee
UnassignedUnassignedReporter
Mike KellyMike KellyLabels
Components
Affects versions
Priority
Major
Details
Details
Assignee
Unassigned
UnassignedReporter
Mike Kelly
Mike KellyLabels
Components
Affects versions
Priority
PagerDuty
PagerDuty
PagerDuty
Created December 28, 2017 at 10:11 PM
Updated September 21, 2021 at 9:16 PM
The
JMXMonitor
doesn't log any details of its exceptions.It has a
catch (Throwable ...)
like this, which means that a large number of possible errors get swallowed, with the only message in the logs being the unhelpful "Monitor - failed! 10.1.2.3".Those log messages should, at least, incorporate the message from the caught exception, if not a full stack trace.