How do I fix: Discovery log is too large and could not be saved. Log length: 20416812, Max length: 16777215.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-03-2022 09:37 AM
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.
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-03-2022 10:25 AM
Hi,
Please refer to this link
Discovery log is too large and could not be saved
Mark Correct or Helpful if it helps.
***Mark Correct or Helpful if it helps.***
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-06-2022 06:21 AM
That's from 3 years ago and doesn't answer the question.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-06-2022 06:53 AM
Hi,
3 Years doesn't necessarily mean it will not work. These tables and properties are in sandiego and in tokyo too.
Here are few other links for you to refer although few years old.
Is it a good idea and safe to set mid server property mid.sm.discolog.max_object_size value to 50000...
The max object size reached the maximum limit of [1000]. To adjust this use the mid property mid.sm....
and then Aman gave you a solution below too you can try that.
You can right click on field label and configure > dictionary there you can increase the length of dictionary.
***Mark Correct or Helpful if it helps.***
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-07-2022 05:23 PM
I have no idea where to set the value Aman suggests.