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

[Feature]: Jaeger SPM - Filter metrics on page by tag #5438

Open
serban-nicusor-toptal opened this issue May 10, 2024 · 3 comments
Open

[Feature]: Jaeger SPM - Filter metrics on page by tag #5438

serban-nicusor-toptal opened this issue May 10, 2024 · 3 comments
Labels
enhancement help wanted Features that maintainers are willing to accept but do not have cycles to implement

Comments

@serban-nicusor-toptal
Copy link

Requirement

Hello!

Is there a feature planned for the SPM page to allow filtering by tags?

We would love to see data per environment but as of now, there's no option to do it in the UI, thus forcing us to have two separate instances to see the different data.

Thanks!

Problem

Having to do duplicate instances for filtering data in the UI.

Proposal

Implement a filtering method based on tags for the SPM ui.

Open questions

Is this planned?

@yurishkuro
Copy link
Member

sounds useful. Please provide more details. How are you doing it now with two instances?

@serban-nicusor-toptal
Copy link
Author

serban-nicusor-toptal commented May 10, 2024

Hey, devs want in some cases to watch the SPM metrics of PROD.
Thus one method of doing this is to just have 2 separate Jaegers. One that ingests lower-envs data and one for prod only.

Edit: If we could have something similar to Tags in the Search pannel, that would be great. When used, that should filter the data just for that tag in the SPM page. Thus not having the need to have 2x Jaegers.
image
Now you can only filter by service name and span kind
image

This is great for single-environment Jaegers, but if you want to have a single instance to handle multiple environments, all that data in SPM will just be merged together and won't be that useful anymore.
Keep in mind, one reason to have a single jaeger is because your traces will be continuous across services thus it's easier to follow. SPM filtering by tags will complement this Jaeger setup and make that data even more useful.

@yurishkuro yurishkuro added the help wanted Features that maintainers are willing to accept but do not have cycles to implement label May 10, 2024
@serban-nicusor-toptal
Copy link
Author

Hello! Any luck with this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement help wanted Features that maintainers are willing to accept but do not have cycles to implement
Projects
None yet
Development

No branches or pull requests

2 participants