We're reclaiming inactive PDIs to keep them available for active builders. Learn what's changing, who's affected, and how to protect your work. Read More

Can't clear scans Sn_SE10241 Discovery schedule names should be related to what is being discovered

HeyMarkWarmack
Tera Expert

I can't clear scans for 'Name' for Impact Scan Findings of:  Sn_SE10241 Discovery schedule names should be related to what is being discovered.


For the Impact app - Impact v8.0.10App id: sn_impact_cust

I am not having luck on clearing the Findings Scan for: 
sn_SE10241 - Discovery schedule names should be related to what is being discovered

I have tried several iterations off Dr Google and SN Docs suggestions for NAME.
My original Discovery Schedule Name format that failed the scan : PRINTERS-Topeka(3 )

              note:  There is a close parentheses but this post makes it a circle.... No space in ( 3 )
I have tried:
PROD-PRINTERS-Topeka(3 )
Prod_Printers_Topeka(3 )

Prod_Printers_Topeka[3]        (tried square brackets)

Prod_Printers_Topeka3         (no parentheses)

ALL the typed versions still appear on the scan findings after rescanning, they still failing the check and I am puzzled why the Name is 'failing'.

 

Supporting Documentation  (This doc shows an example Name of:  CIM - SMI-S - Storage Controllers)
 
A search yielded this suggestion, but none has worked:
Examples:
Location-Based: [Location Code] - [Environment] - [Asset Type] (e.g., NYC-Prod-Servers, LON-Dev-Network)
Segment/Network-Based: [Site/Building] - [IP Range/Subnet] (e.g., BldgA-10.10.2.x, DMZ-Web-10.50.4.x)
Function-Based: [Environment] - [Function] (e.g., Prod-Databases, Staging-Windows-Servers)
Cloud-Based: [Cloud Provider] - [Account Name] - [Region] (e.g., AWS-Prod-US-East)
 

I have not find any Naming examples that work.  Please let me know if you have something that works.

 

Small issue, but trying not to override these but this one is frustrating.

Thank you!  Appreciate any feedback.

Mark

0 REPLIES 0