Discovery log too large and not saved

[Patrick Oudshoo]

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.

[VaranAwesomenow]

What pattern is this and what level of logging is enabled ?

[Patrick Oudshoo]

Hi Anil,

This is the Out-of-the-box Network Switch pattern, but the switch discovered has slave switches and therefore more needs to be done by discovery than for a switch without slaves.
I suspect at least that is why I end with a log that is too large.

[samira2]

Naturally, Docker utilizes the json-document log driver and recoveries those logs in the overlay envelope. Docker doesn't confine the size of the documents or what number of log records there can be for a solitary compartment. On the off chance that you keep on running that compartment, the log document will develop as long as it has drive space to do as such. Fortunately, it's entirely simple to set these cutoff points.

Sarkari Result Pnr Status 192.168.l.l

[Patrick Oudshoo]

Hi Samira,

Thanks for your response.

However it seems for you it is entirely simple to set these cutoff points. Can you please enlighten me and share on how I can set these cutoff points myself.
At lest, how I understand your response, this will result in showing me my Discovery log that I am so badly looking for?!?