Open ascoppa opened 1 week ago
Hi @ascoppa! Thanks for letting us know about the issue. Between agent verisons 9.0.0
and 9.10.2
, we started using a different endpoint to get the cluster name. This helped with performance but might be causing the error you're seeing.
We don't officially support Elasticsearch versions below 7, but we want to to explore this issue a little further to see if this is an Elasticsearch version issue or something else. You also make a good point about the number of errors we're generating, so we're going to look into reducing those.
Description
After upgrading the New Relic agent from version
9.0.0
to9.10.2
, we began encountering multiple signature errors on our monitoring systems. Upon further inspection, the following errors were identified in our logs:and immediately below this ☝️ line
These requests are being done by new relic ruby agent apparently as part of a health check routine (they trigger multiple times over time) so as a workaround we decided to disable new relic instrumentation on Elasticsearch by setting the following environment variable
NEW_RELIC_INSTRUMENTATION_ELASTICSEARCH
todisabled
. After doing so, the signature errors disappeared.Expected Behavior
No signature errors should appear during the health check routine.
Your Environment
Note
If you need any further clarification, please don't hesitate to ask. Thank you.