Discovery log too large and not saved
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-08-2019 08:08 AM
All,
For some debugging, I really need the discovery log that is currently NOT saved since it is too big.
See my attachment and the statement in there 'Discovery log is too large and could not be saved'.
Any way to enlarge this, just for debugging purposes?!?
This since my pattern extension seems not to run but have no clue why.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-03-2019 05:40 AM
Not sure if this will work, but try to update the "log" column max length under table "sa_discovery_log". Let me know if that works.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-09-2019 10:58 PM
Hi,
we encountered the same problem and support came back with this answer:
This is a known issue on the Java code and has been fixed in New York Patch 3, Orlando, and now is ready to be tested on Madrid Patch 9. If a discovery pattern log exceeds the default size value of 4096000. The discovery pattern log will not be saved and the discovery log will have the following message: "Discovery log is too large and could not be saved"
They also pointed out the following knowledge article: KB0749511 : Increasing the length of sa_discovery_log.log dictionary does not fix "Discovery log is ...
So Patricks answer would actually be the solution if not for this bug.