Uploaded image for project: 'OpenNMS'
  1. OpenNMS
  2. NMS-10261

newSuspect events do not get processed when they reference a missing system id (aka distpoller)

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Fixed
    • 22.0.1
    • 22.0.2, Meridian-2018.1.0
    • None
    • Security Level: Default (Default Security Scheme)
    • None
    • Horizon - July 11th 2018, Horizon - July 18th 2018

    Description

      While debugging a case where newSuspect events were not being processed - they appeared in provisiond.log, but not further action was taken - I found that these were being discarded due to the fact that the monitoring system id, or distpoller id that was referenced in the events was not present in the database.

      We perform this lookup so that the newSuspect events generated by a given monitoring system are processed at the same location, however we should continue to process the events at the default location if the system is not found.

      Attachments

        Activity

          People

            j-white Jesse White
            j-white Jesse White
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.