Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
AI OnAI Off
Bad request from /find_v2/{*query} New Relic error
Hi,
_track might return 400 errors depending on the query string. There are a number of possible validation errors (should be returned in the response if you get hold of it). The most common issue would be that q (i.e the query to track is not set).
/Henrik
Oct 24, 2017 9:11
Thanks!
A suggestion might be to use 422 (unprocessable entity) instead. I think New Relic won't pick up that as an actual error that affects the error rate stats.
There is the possibility to exclude http error codes in NR also:
https://docs.newrelic.com/docs/agents/net-agent/configuration/net-agent-configuration#error_collector
Not sure if this is an option for DXC Service though.
Oct 24, 2017 9:35
Seeing this in a couple of different site's New Relic error stats. Not massive counts but occuring every now and then.
/find_v2/{*query} 400 Bad Request
Listing occurences seems like /find_v2/_track is the path.
Haven't gotten hold of a complete occurence request data yet but someone might already know a cause or fix?