-
Notifications
You must be signed in to change notification settings - Fork 205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
http server 4xx configuration #2037
Conversation
6ab5257
to
14c2f2f
Compare
@@ -228,6 +228,7 @@ public String toString() { | |||
// this is needed to unblock customer, but is not the ideal long-term solution | |||
// https://portal.microsofticm.com/imp/v3/incidents/details/266992200/home | |||
public boolean disablePropagation; | |||
public boolean captureHttpServer4xxAsError = true; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i saw the IcM 282327358 that is asking to treat 4xx response as success not error. rename?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this naming is a bit better from otel perspective, as the default in otel is not to capture server 4xx as error (but also not to capture it as success, there's a third option in otel - UNSET)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is the config customer will be using.. if they wants 4xx as success, they will set this flag to false. unset will return true. yeah, it works.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
azure doc needs to be updated.
let's track this via statsbeat. |
No description provided.