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

Aggregate metrics results of TestRun #413

Closed
or3330 opened this issue Jun 7, 2024 · 3 comments
Closed

Aggregate metrics results of TestRun #413

or3330 opened this issue Jun 7, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@or3330
Copy link

or3330 commented Jun 7, 2024

Feature Description

As part of my usage in k6-operator, I wanted to get as a result of a TestRun my custom metrics and use it as part of the validations in my integration test flow.

I noticed that aggregated metrics from all of the TestRun pods on the operator manager level is not available, and I think it's a pretty important feature.

I will be happy to take this on!

Suggested Solution (optional)

I thought about using some sort of shared volume to send the metrics results of each pod as files, and then aggregate them on the manager level when the test finishes, and create a file with the name of the TestRun under some predefined folder on the manager pod volume.

Already existing or connected issues / PRs (optional)

No response

@or3330 or3330 added the enhancement New feature or request label Jun 7, 2024
@or3330 or3330 changed the title Aggregate metrics of TestRun feat: Aggregate metrics results of TestRun Jun 7, 2024
@or3330 or3330 changed the title feat: Aggregate metrics results of TestRun Aggregate metrics results of TestRun Jun 7, 2024
@yorugac
Copy link
Collaborator

yorugac commented Jun 7, 2024

Hi @or3330, it is an important feature but it's outside of scope for k6-operator itself. We currently provide aggregation as part of our Grafana Cloud k6 (GCk6). More on that can be read here:
https://grafana.com/docs/grafana-cloud/testing/k6/

Specifically with k6-operator, there are two modes supported by GCk6:

  • running cloud output tests, with --out cloud (readme docs)
  • running PrivateLoadZone, docs

Would those work for you?

@or3330
Copy link
Author

or3330 commented Jun 7, 2024

Hi @yorugac, thanks for the quick response!

I actually wanted to self host the solution, and not use an external provider.

@yorugac
Copy link
Collaborator

yorugac commented Jun 19, 2024

@or3330, sorry for the delay. I understand the problem but it is outside of k6-operator scope. The only way I can see it kind of partially supported by us is via distributed mode in k6 (issue) but it is still quite far away and most of that work will be outside of k6-operator anyway.

As mentioned, our solution for aggregation is cloud-based and not self-hosted. Of course, it is possible to set something self-hosted as k6 allows to stream its metrics to external DBs, like Prometheus. But it will not be a trivial task, and k6-operator project is simply not meant for that.

I'm closing the issue. Feel free to open another if there's a k6-operator specific question and / or comment in k6 repo about aggregation.

@yorugac yorugac closed this as completed Jun 19, 2024
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