To troubleshoot the sensor issues, follow the steps outlined in the technical documentation.
Additionally, you can get more output logs and a dump with symbols by tagging one of the sensors as a
debug. Here is how to do it:
Stop the sensor/service
Go to the sensor details page
latesttag to the sensor
debugtag to the sensor
Start the sensor
This will allow you to see more logs and get a better understanding of the issue.
For memory or CPU issues, it is recommended to run a
get_debug_info command on that sensor from the Console in the web app while it's under heavy CPU/memory. Please send the output to the LimaCharlie support team - it gives us a full trace of where CPU/memory is being used.