Currently, have a few error messages Splunk has been configured to look for to determine if the Devtest Coordinator/Registry etc are becoming unstable. We would like to know if these messages are still valid search terms and if there are additional error messages which we should look for to identify potential issues requiring admin assistance. This is to continue proactive support for our DevTest implementation.
index=app_rental_onprem sourcetype=rental_ca_registry java.lang.OutOfMemoryError
index=app_rental_onprem sourcetype=rental_ca_coordinator "Timeout putting events on internal event handler queue. This usually indicates an overloaded system."
index=app_rental_onprem sourcetype=rental_ca_registry "java.lang.OutOfMemoryError: GC overhead limit exceeded"
index=app_rental_onprem sourcetype=rental_ca_coordinator "java.lang.OutOfMemoryError"
"Error capturing report data for Database: The database writer cannot keep up with the number of events being generated
com.itko.lisa.test.EventDeliveryException: The database writer cannot keep up with the number of events being generated "
"Heap size approaching limit"
Enterprise Dashboard or Registry alert:
"java.sql.SQLException: Connections could not be acquired from the underlying database!"
"Error in query Solr"
Registry, Coordinartor or VSE alert:
"java.lang.OutOfMemoryError: unable to create new native thread"