• Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Assets Discovery
    • None
    • 0
    • 3
    • 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.

      Problem Statement

      As an Administrator, I want to be able to monitor Asset Discovery Scans, from start to finish, directly within the Discovery App.

      Issue Details:

      The Asset Discovery App is designed to run a network scan periodically, collecting the scanned Information.

      When the scans are in progress, data is written to a file which is eventually uploaded to Jira. Due to the nature of these scans, it can take a significant amount of time for the scan to complete, and therefore Administrators want a simple way to monitor the situation.

      Idea:

      Administrators, who are managing and running these scans, would like a way to easily monitor these scans directly within the Discovery Application.

      Perhaps we can add a "Monitor" tab to the Discovery App and see the current status of an active scan, along with both scheduled, and completed, data.

      Work Around

      Right now, if Discovery is running as a service, administrators can use

      discovery.exe -stsc
      

      to check and run any pending scans.

      Others have had some success monitoring the log files generated by the scan

            [JSDSERVER-14891] Add Ability to Monitor Discovery Scans within the App

            SET Analytics Bot made changes -
            UIS Original: 1 New: 0
            SET Analytics Bot made changes -
            Support reference count New: 3
            Marek Parfianowicz made changes -
            Status Original: Gathering Interest [ 11772 ] New: Not Being Considered [ 11776 ]

            Atlassian Update – 24 Sep 2024

            Hi everyone,

            We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to close it as Not being considered.

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. Our team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details.

            We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

            Marek Parfianowicz added a comment - Atlassian Update – 24 Sep 2024 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to close it as Not being considered . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. Our team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.
            SET Analytics Bot made changes -
            UIS New: 1
            Patrick Turbett created issue -

              Unassigned Unassigned
              6a1ad6d343e3 Patrick Turbett
              Votes:
              4 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: