You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since rejected response can't have labeled path, there is no way to know exactly what request is rejected. Can we add StatusGroup and Path to requests?
The text was updated successfully, but these errors were encountered:
Hi @jundong321.
Indeed, this is a conscious design decision that unhandled requests have a fixed label
You must also be careful about cardinality: see here
An attacker can hammer your service with random paths requests that will blow up your registry and also increase costs if you export the metrics to an centralized logging service like datadog or AWS CloudWatch.
There is no easy way to change this behavior. I would advise use a custom rejection handler with a specific handleNotFound that will log the rejected path, or other type of rejection you want to log.
Concerning the status group, it should be available on the rejected responses.
Since rejected response can't have labeled path, there is no way to know exactly what request is rejected. Can we add StatusGroup and Path to requests?
The text was updated successfully, but these errors were encountered: