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

Cannot debug Telemetry persistence on Sentinel

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 24.1.0
    • Fix Version/s: 25.0.0
    • Component/s: Sentinel
    • Security Level: Default (Default Security Scheme)
    • Labels:
    • Sprint:
      Horizon 2019 - September 11th, Horizon 2019 - September 18th

      Description

      I remember that with Telemetry within OpenNMS, it was possible to show in DEBUG mode all the persisting work, specially when compiling, running and showing debug messages from the Groovy scripts that will take care of preparing the CollectionSets.

      This is the information I cannot see on karaf.log for Sentinel, meaning that I don't know why Sentinel is not persisting the Telemetry data. It is receiving the data, as Minion is properly sending it, and Sentinel is properly consuming it.

      In other words, when Sentinel consumes or extract a message from the Telemetry topics (as I'm using Kafka), I don't know what it does next, meaning if there is an error, I'm not aware of it.

      To clarify what's required:

      1) Be able to see the raw message in human-readable form on the logs, from the original GBP message sent by the Nexus switch.
      2) Be able to see debug messages generated from within the Groovy script on the logs.
      3) Be able to see any error message generated from within the script on the logs.

      The above should work regardless if Sentinel or OpenNMS is used to analyze telemetry data.

      This is important because in case of Cisco the data provided by the switches come on an undocumented form, and depends on how telemetry was configured. For this reason, to build the Groovy script, a human-readable content of the data is required; otherwise, the script cannot be implemented. Then, once the script is implemented, it is very important to be able to see debug messages and errors generated from the script, as there are no tools to validate the implementation of the script in question, meaning either OpenNMS or Sentinel must be used for this purpose.

        Attachments

          Activity

            People

            • Assignee:
              mvr Markus von RĂ¼den
              Reporter:
              agalue Alejandro Galue
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: