Skip to content
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

Give possibility to aggregate RUM Service Traces URL #930

Open
DominikJura opened this issue May 11, 2022 · 1 comment
Open

Give possibility to aggregate RUM Service Traces URL #930

DominikJura opened this issue May 11, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@DominikJura
Copy link

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
@DominikJura DominikJura added the enhancement New feature or request label May 11, 2022
@xgouchet
Copy link
Member

Hi @DominikJura , thanks that's indeed an interesting feature request, we'll take a look into this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants