When running the Prometheus OpenMetrics integration for Kubernetes, you notice restarts and gaps in data sent to New Relic.
When running the Prometheus OpenMetrics integration for Kubernetes with 500K data points per minute, be sure to set these limits:
- CPU limit: 1 core
- Memory limit: 1Gb
Recommendation: Always run the Kubernetes scraper with one replica.
Adding more replicas will result in duplicated data. If the CPU and memory limits are not sufficient, this can result in restarts and gaps in the data.
To check the status and restart events for the scraper:
kubectl describe pod -l "app=nri-prometheus"
If you need more help, check out these support and learning resources:
- Browse the Explorers Hub to get help from the community and join in discussions.
- Find answers on our sites and learn how to use our support portal.
- Run New Relic Diagnostics, our troubleshooting tool for Linux, Windows, and macOS.
- Review New Relic's data security and licenses documentation.