When importing multiple scan to JSM from cloud, the existing data is overwritten.

Harla Batinovic
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 22, 2024

I have two servers running Discovery Tool scans. They are uploaded via the cloud to the same Schema in JSM. They use the same token on both servers for the transfer. There is no overlap of servers being scanned.

Server 1:

  • LINUX scan of 6 servers at 12:05 AM - takes about 5 minutes to scan
  • Win scan of 6 servers at 12:20 AM - takes about 5 minutes to scan
  • Win scan of 60 servers at 12:40 AM - takes about 2 hours to scan

Server 2:

  • Win scan of 6 servers at 12:15 AM  - takes about 5 min
  • Win scan of 56 servers at 1:00 AM - takes about 2 hours

All 5 server scans are imported into the same schema in JSM. However, when I look after they are completed, many of the status in Host tab say  NOT FOUND. 

It appears only last scan is showing the results and deletes the results from the other imports. 

Has anyone else had this issue and how did it get resolved? 

1 answer

2 votes
Kristen Riddle August 22, 2024

It sounds like you're dealing with an issue where multiple Discovery Tool scans are being imported into the same schema in Jira Service Management (JSM), and the results are overwriting each other. The "NOT FOUND" status likely means that when the last scan is imported, it replaces the data from the previous scans instead of merging it.

By making a few changes to how you're handling imports and data, you should be able to prevent one scan's results from overwriting another's. Hopefully, this helps you get to the bottom of the issue!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events