How do I fix: Discovery log is too large and could not be saved. Log length: 20416812, Max length: 16777215.

jrmckins
Kilo Expert

I get this message when discovering Nutanix:

Discovery log is too large and could not be saved. Log length: 20416812, Max length: 16777215.

1. Where is the "Max Length" defined? I don't see "16777215" set anywhere.
2. How do I fix this? I set mid.sm.discolog.max_log_size to "24417384", rebooted the mid server, and I still get that same message.
12 REPLIES 12

Aman Kumar S
Kilo Patron

The error message 'Discovery log is too large and could not be saved' appears in the discovery log. Increasing the length of sa_discovery_log.log dictionary will fix the issue.

Best Regards
Aman Kumar

Where do I set that? 

Ram Devanathan1
ServiceNow Employee
ServiceNow Employee

While one solution is increasing the size, this may not always be feasible and cannot be a permanent solution.

you could reduce retention level - to a few days instead of default so older logs get cleaned up faster.

https://docs.servicenow.com/bundle/quebec-it-operations-management/page/product/discovery/reference/...

can you check for below logging level setting (system property) - if it is changed to say 'debug', bring it back to defaults (info, warn, error). debug logs are to be used during troubleshooting but not for permanent usage as there's a a ton of details given out here.

glide.cmdb.logger.source.identification_engine

https://docs.servicenow.com/en-US/bundle/sandiego-servicenow-platform/page/product/configuration-man...