Discovery Admin Workspace settings not sticking

nebula
Tera Guru

In Discovery Admin Workspace, under Settings, my Configure time scale selection and the ability to enable Anomaly detection does not save. Anyone else have this problem or are aware of this issue?

 

Steps taken:

  1. Workspace > Discovery Admin Workspace
  2. Click Settings
  3. Select Configure time scale drop down.
  4. Click the Enable anomaly detection button.
  5. Click Save on the top right.

 

I will see the successful message "Your setting changes have been saved." but when I refresh, it reverts back as if I never selected anything. I've even duplicated the tab and again, do not see my changes.

 

Per documentation and community posts, after clicking Save, it should stick.

https://www.servicenow.com/docs/bundle/yokohama-it-operations-management/page/product/discovery/conc...

 

https://www.servicenow.com/community/itom-blog/discovery-admin-workspace-may-2025-release-updates/ba... 

1 REPLY 1

Varsha Rao
ServiceNow Employee
ServiceNow Employee

Both the timescale selection and Anomaly detection can be updated via System property.

  • To enable Anomaly detection, please update the system property  'sn_disco_workspace.discovery_schedule_anomaly_detection_disabled' to false.
  • To configure timescale configuration, please update 'sn_disco_workspace.discovery_stats_time_scale' 

Here's a mapping of the system properties for the property configurations allowed via Settings tab on Discovery Admin Workspace:

  1. To configure dashboard time scale:  sn_disco_workspace.discovery_stats_time_scale  
  2. To disable anomaly detection: sn_disco_workspace.discovery_schedule_anomaly_detection_disabled 
  3. To change the anomaly detection method: sn_disco_workspace.discovery_schedule_anomaly_detection_method
  4. For Anomaly detection sensitivity: sn_disco_workspace.discovery_schedule_anomaly_ml_model_sensitivity 
  5. Runtime threshold: sn_disco_workspace.discovery_schedule_runtime_anomaly_threshold
  6. CIs discovered threshold: sn_disco_workspace.discovery_schedule_cis_discovered_anomaly_threshold
  7. Error threshold: sn_disco_workspace.discovery_schedule_error_anomaly_threshold

Hope this helps.