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

Built In wss sessions is creating too many trends #33

Closed
mkadirtan opened this issue Jan 17, 2023 · 7 comments · Fixed by #60
Closed

Built In wss sessions is creating too many trends #33

mkadirtan opened this issue Jan 17, 2023 · 7 comments · Fixed by #60
Labels
enhancement New feature or request

Comments

@mkadirtan
Copy link
Contributor

Hi, the built-in metrics for ws_session_duration_seconds etc. include the websocket url. Which is great, but it also includes the query parameters. I'm testing for a socket.io server and the query parameter include user token. That causes k6 to create as many histograms as there are different users. Is it possible to ignore query parameters for this? Maybe we can add this as an option to environment variable?

@olegbespalov
Copy link
Contributor

Hi @mkadirtan

Thanks for the feedback!

You're right, and we have to introduce some workarounds for that.

Let us come up with a decision on how to handle it better (aligning with the core grafana/k6 which has similar changes) and probably implement it ☺️

@olegbespalov olegbespalov added the enhancement New feature or request label Jan 23, 2023
@mkadirtan
Copy link
Contributor Author

Thanks for the reply, maybe we can use this issue to track progress

@konovalovsergey
Copy link

Hi @olegbespalov
It's reasonable to follow logic of k6 after v0.41.0 (grafana/k6#2703) - replace "url" tag with "name" tag if it exists.
What you will say to that?

@konovalovsergey
Copy link

Сan I help with the implementation of this functionality? If this is the right direction. Task doesn't look very difficult.

@olegbespalov
Copy link
Contributor

Hey @konovalovsergey ! Thanks for offering the help! ☺️

Let me quickly confirm with the team that this is the direction in which we want to evolve, and I (or anybody else from the core team) will get back to you!

@olegbespalov
Copy link
Contributor

Hey @konovalovsergey !

I'm sorry for not getting back to you sooner. After an internal conversation, we concluded that the websockets tags (along with the other protocol tags like gRPC) should work the same way HTTP tags work. If the name tag is defined, url should be overwritten with the name's value.

Сan I help with the implementation of this functionality? If this is the right direction. Task doesn't look very difficult.

So if you still want to contribute by implementing this functionality, feel free to do that 👍

@mkadirtan
Copy link
Contributor Author

@olegbespalov happy you guys came up with a decision on this one 🥳 . @konovalovsergey I hope you still want to implement this, but if you don't, please let me know, then I can have a look at it. But, of course, prefer you to do it 🙏

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

Successfully merging a pull request may close this issue.

3 participants