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
Server side tracing can be disabled by specifying a skip pattern which is used to match with HTTP path UriInfo.getPath(). If the regex matches with HTTP path then tracing for the given server request is disabled even if the method or class is annotated with @Traced. The configuration does not disable any outbound request made from the disabled server endpoint.
UriInfo.getPath() does not include the context root of the app. What if we have 2 apps that have the same paths but just want to skip one but not the other.
The text was updated successfully, but these errors were encountered:
properties files are scoped per app so the problem is only when using "global" sources like environmental or system properties which are reflected to all deployments. So the second approach is to clarify that when using global configs the URL is applied to all deployments.
The other issue with the current spec is that UriInfo.getPath() does not include application path so even two distinct apps would disable tracing for the same endpoint.
I think the way to go is 1. - specify the full URL (without host port schema..) in the skip pattern.
In the spec we mentioned
Server side tracing can be disabled by specifying a skip pattern which is used to match with HTTP path UriInfo.getPath(). If the regex matches with HTTP path then tracing for the given server request is disabled even if the method or class is annotated with @Traced. The configuration does not disable any outbound request made from the disabled server endpoint.
UriInfo.getPath() does not include the context root of the app. What if we have 2 apps that have the same paths but just want to skip one but not the other.
The text was updated successfully, but these errors were encountered: