-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
End of test information in collector #154
Comments
|
|
Oh, I just remembered, you can just check We need to solve this for distributed execution (#140) somehow, but we can think about it later. I have a couple of ideas, ranging from querying the backend to writing metric information to the cluster's datastore. |
Ok, but this way I need to do a lot of bookkeeping to figure out what is tainted or not in the end. And this is also only gives me access to the boolean part of the threshold. Frontend is also in need of presenting the value and the level for the threshold (preferably without having to parse the threshold expression). That is why I'd like the engine to compile together this information about the threshold at the end of the test and sent to collectors. |
I'll have to think about how to do this, the code surrounding thresholds is somewhat messy and needs some cleaning before it can be exposed to anything |
Also |
I think what we need here is to rework the Metric struct a bit; thresholds, submetrics and the sink should be available within it. |
Working on this right now. |
You can now access thresholds from Metric objects, working on getting derived metrics in there too… |
We'd like to have access to more information in the collector when a test finishes. Specifically:
The text was updated successfully, but these errors were encountered: