Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-11071

Discovery Scanner should be able to generate more detailed debug logs for Agent scan Triggering from the Discovery tool

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Assets Discovery
    • None
    • 2
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Currently, the debug logs generated by the Discovery scanner are very limited and it doesn't include any debug log information on the Agent scan Triggering from the Discovery tool. It should include detailed logs on the Agent scan initiation, running, or termination status.  When the Agent scan gets terminated or not initiated or hangs it should produce more debug information in the logs.

            [JSDSERVER-11071] Discovery Scanner should be able to generate more detailed debug logs for Agent scan Triggering from the Discovery tool

            Allan O'Rourke made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 1014970 ]
            SET Analytics Bot made changes -
            Support reference count New: 2
            Marek Parfianowicz made changes -
            Status Original: Gathering Interest [ 11772 ] New: Future Consideration [ 11775 ]
            Prabhu Subramaniyan made changes -
            Summary Original: Discovery Scanner should be able to generate more detailed debug logs for troubleshooting New: Discovery Scanner should be able to generate more detailed debug logs for Agent scan Triggering from the Discovery tool
            Prabhu Subramaniyan made changes -
            Description Original: Currently, the debug logs generated by the Discovery scanner is very limited and it doesn't include any debug log information on the scan initiation, running, or termination status.  When the scan gets terminated or not initiated it should produce more debug information in the logs. New: Currently, the debug logs generated by the Discovery scanner are very limited and it doesn't include any debug log information on the Agent scan Triggering from the Discovery tool. It should include detailed logs on the Agent scan initiation, running, or termination status.  When the Agent scan gets terminated or not initiated or hangs it should produce more debug information in the logs.
            Prabhu Subramaniyan created issue -

              Unassigned Unassigned
              f75285566e0c Prabhu Subramaniyan
              Votes:
              3 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: