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
Is your feature request related to a problem? Please describe.
Now when You report traces with URL's that have wildcards like:
-> api/v1/users/{userId}/emails/{emailId}:
api/v1/users/1/emails/33
api/v1/users/1/emails/33
In Datadog they are visible as separate endpoints and not aggregated, and should be visible as:
api/v1/users/*/emails/* after clicking it should go to specific list of traces that match wildcard url
Which is confusing and it is hard to evaluate how big problem is.
Describe the solution you'd like
There can be two possible solutions:
You can expose in Android SDK Trace config, where You provide url that have wildcards, and based on input change reported URL to Datadog so they will be visible correctly
In Datadog Services Website add mechanism that based on reported url's aggregates them and AI underneath creates wildcards so they are visible correctly
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Now when You report traces with
URL's
that have wildcards like:-> api/v1/users/{userId}/emails/{emailId}:
In Datadog they are visible as separate endpoints and not aggregated, and should be visible as:
api/v1/users/*/emails/* after clicking it should go to specific list of traces that match wildcard url
Which is confusing and it is hard to evaluate how big problem is.
Describe the solution you'd like
There can be two possible solutions:
The text was updated successfully, but these errors were encountered: