Error sending data to Wavefront: java.lang.IllegalStateException: Connection pool shut down. Proxy does not resurrect and requires manual intervention.
Too much data is being sent or scrapped by to the Wavefront Proxy. The proxy does not have the resources to keep up with the ingestion levels.
Upgrade to Wavefront Proxy 13.7 [GA Release], which includes an Updated Netty netty-bom to version 4.1.108.Final to resolve CVE-2024-29025.
Once upgraded, proxy crashes may continue for other reasons but now will resurrect the pod automatically.
Additional steps to resolve other OOM issues AFTER upgrading the proxy begin with understand the data patterns and data needs of each cluster environment.
Once an understanding of your data patterns and needs you can:
wavefrontHQ/observability-for-kubernetes - wavefront-full-config.yaml
wavefrontHQ / Observability for Kubernetes - The Kubernetes Metrics Collector supports filtering metrics and events.
Defining proxy pre-processor rules - Advanced-proxy-preprocessor-rules
Install and Manage Wavefront Proxies - See Section: Proxy Host Requirements
Wavefront Proxy - Section: Production Environment: Team of Proxies Load Balancer
Monitor Wavefront Proxies - Section: Examine the Health and Usage of a Proxy with the Proxy Dashboard