Cumulocity IoT Feedback Portal
https://getsupport.softwareag.com/servicedesk/customer/portal/2/SI-509929
In the suport ticket we were informed that it is default behvior of cumulocity that the logs of a microservice are lost as soon as it is restarted.
If we have a problem with a service and cumulocity is restarting it, it is extremely helpful to have the respective logs available, without, an error search is almost impossible.
Hey Andrew, the team is currently working on this functionality, please subscribe to the Cumulocity Change Logs to be updated once it is available: https://cumulocity.com/docs/change-logs/
It has been over a year on the original request. Are there any updates related to ease of gathering microservice logs?
Hello Nick,
thanks first of all for the answer. We know the work arround. But i is very unhandy as well as timeconsuming especially if you have serveral customer accounts at the cumulosity and a problem is occuring frequently.
We are really looking forward for a more approachable solution.
Thank you for you feedback! We are looking into improving logs handling with hosted microservices. This would be refined after internal migration to managed Kubernetes is done.
For now logs are not deleted, but unfortunately not exposed to the application layer.
Current workaround is requesting missing logs from support