Restarting the microservice would appear to have cleared the log, but in fact it merely “clear screen” if you will and append to the log. If you do a search of old messages, you will find them. Therefore, the log is not cleared.
Any other suggestions?
I’d be interested to hear about the use case for clearing the log entirely.
One thing that should work is to delete the microservice and upload it again. That way the application has a new id and should not be associated with any old logs.
unfortunately, I cannot give you a definite answer on this. I think as microservice logs are stored separately, they should not be included in the storage size.
We’ve tried removing the microservice and reinstalling it but we are still seeing old messages when we did a search.
The reason why we were wanting to clear the log is so that during debugging, we will not be confused by old errors or diagnostic messages from an earlier version of the microservice. Looks like we just have to be mindful of the timestamp in the absence of being able to clear the log.
Btw, what is the size of the log so I get a sense of how soon the log could persist until overwritten.