-
Notifications
You must be signed in to change notification settings - Fork 15
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
Show whether the latest measurement of metric has been done with the current configuration of its source(s) #3134
Comments
18 tasks
Duplicates/overlaps #920. |
8 tasks
fniessink
added a commit
that referenced
this issue
May 10, 2024
In the UI, show a metric as needing a measurement because the source parameters were recently changed. Implemented by: - In the collector: adding a hash of the source parameters to measurements. - TODO: In the API-server: compare the hash of the latest measurement with the hash of the current configuration when adding recent measurements to a report and mark the metric as outdated. - TODO: In the UI: show metrics as needing a measurement if the last measurement is outdated. Open issues: - Seeing the source parameter hash is only useful in the most recent measurement, should the hash be removed from the latest measurement before inserting a new one? Closes #3134.
fniessink
added a commit
that referenced
this issue
May 10, 2024
In the UI, show a metric as needing a measurement because the source parameters were recently changed. Implemented by: - In the collector: adding a hash of the source parameters to measurements. - TODO: In the API-server: compare the hash of the latest measurement with the hash of the current configuration when adding recent measurements to a report and mark the metric as outdated. - TODO: In the UI: show metrics as needing a measurement if the last measurement is outdated. Open issues: - Seeing the source parameter hash is only useful in the most recent measurement, should the hash be removed from the latest measurement before inserting a new one? Closes #3134.
fniessink
added a commit
that referenced
this issue
May 10, 2024
In the UI, show a metric as needing a measurement because the source parameters were recently changed. Implemented by: - In the collector: adding a hash of the source parameters to measurements. - TODO: In the API-server: compare the hash of the latest measurement with the hash of the current configuration when adding recent measurements to a report and mark the metric as outdated. - TODO: In the UI: show metrics as needing a measurement if the last measurement is outdated. Open issues: - Seeing the source parameter hash is only useful in the most recent measurement, should the hash be removed from the latest measurement before inserting a new one? Closes #3134.
fniessink
added a commit
that referenced
this issue
May 10, 2024
In the UI, show a metric as needing a measurement because the source parameters were recently changed. Implemented by: - In the collector: adding a hash of the source parameters to measurements. - In the API-server: compare the hash of the latest measurement with the hash of the current configuration when adding recent measurements to a report and mark the metric as outdated. - TODO: In the UI: show metrics as needing a measurement if the last measurement is outdated. Open issues: - Seeing the source parameter hash is only useful in the most recent measurement, should the hash be removed from the latest measurement before inserting a new one? Closes #3134.
fniessink
added a commit
that referenced
this issue
May 10, 2024
In the UI, show a metric as needing a measurement because the source parameters were recently changed. Implemented by: - In the collector: adding a hash of the source parameters to measurements. - In the API-server: compare the hash of the latest measurement with the hash of the current configuration when adding recent measurements to a report and mark the metric as outdated. - TODO: In the UI: show metrics as needing a measurement if the last measurement is outdated. Open issues: - Seeing the source parameter hash is only useful in the most recent measurement, should the hash be removed from the latest measurement before inserting a new one? Closes #3134.
fniessink
added a commit
that referenced
this issue
May 10, 2024
In the UI, show a metric as needing a measurement because the source parameters were recently changed. Implemented by: - In the collector: adding a hash of the source parameters to measurements. - In the API-server: compare the hash of the latest measurement with the hash of the current configuration when adding recent measurements to a report and mark the metric as outdated. - TODO: In the UI: show metrics as needing a measurement if the last measurement is outdated. Open issues: - Seeing the source parameter hash is only useful in the most recent measurement, should the hash be removed from the latest measurement before inserting a new one? Closes #3134.
fniessink
added a commit
that referenced
this issue
May 10, 2024
In the UI, show a metric as needing a measurement because the source parameters were recently changed. Implemented by: - In the collector: adding a hash of the source parameters to measurements. - In the API-server: compare the hash of the latest measurement with the hash of the current configuration when adding recent measurements to a report and mark the metric as outdated. - TODO: In the UI: show metrics as needing a measurement if the last measurement is outdated. Open issues: - Seeing the source parameter hash is only useful in the most recent measurement, should the hash be removed from the latest measurement before inserting a new one? Closes #3134.
fniessink
added a commit
that referenced
this issue
May 10, 2024
In the UI, show a metric as needing a measurement because the source parameters were recently changed. Implemented by: - In the collector: adding a hash of the source parameters to measurements. - In the API-server: compare the hash of the latest measurement with the hash of the current configuration when adding recent measurements to a report and mark the metric as outdated. - TODO: In the UI: show metrics as needing a measurement if the last measurement is outdated. Open issues: - Seeing the source parameter hash is only useful in the most recent measurement, should the hash be removed from the latest measurement before inserting a new one? Closes #3134.
fniessink
added a commit
that referenced
this issue
May 13, 2024
In the UI, show a metric as needing a measurement because the source parameters were recently changed. Implemented by: - In the collector: adding a hash of the source parameters to measurements. - In the API-server: compare the hash of the latest measurement with the hash of the current configuration when adding recent measurements to a report and mark the metric as outdated. - TODO: In the UI: show metrics as needing a measurement if the last measurement is outdated. Open issues: - Seeing the source parameter hash is only useful in the most recent measurement, should the hash be removed from the latest measurement before inserting a new one? Closes #3134.
fniessink
added a commit
that referenced
this issue
May 13, 2024
In the UI, show a metric as needing a measurement because the source parameters were recently changed. Implemented by: - In the collector: adding a hash of the source parameters to measurements. - In the API-server: compare the hash of the latest measurement with the hash of the current configuration when adding recent measurements to a report and mark the metric as outdated. - TODO: In the UI: show metrics as needing a measurement if the last measurement is outdated. Open issues: - Seeing the source parameter hash is only useful in the most recent measurement, should the hash be removed from the latest measurement before inserting a new one? Closes #3134.
fniessink
added a commit
that referenced
this issue
May 13, 2024
In the UI, show a metric as needing a measurement because the source parameters were recently changed. Implemented by: - In the collector: adding a hash of the source parameters to measurements. - In the API-server: compare the hash of the latest measurement with the hash of the current configuration when adding recent measurements to a report and mark the metric as outdated. - TODO: In the UI: show metrics as needing a measurement if the last measurement is outdated. Open issues: - Seeing the source parameter hash is only useful in the most recent measurement, should the hash be removed from the latest measurement before inserting a new one? Closes #3134.
fniessink
added a commit
that referenced
this issue
May 13, 2024
In the UI, show a metric as needing a measurement because the source parameters were recently changed. Implemented by: - In the collector: adding a hash of the source parameters to measurements. - In the API-server: compare the hash of the latest measurement with the hash of the current configuration when adding recent measurements to a report and mark the metric as outdated. - In the UI: show metrics as needing a measurement if the last measurement is outdated. Open issues: - Seeing the source parameter hash is only useful in the most recent measurement, should the hash be removed from the latest measurement before inserting a new one? Closes #3134.
fniessink
added a commit
that referenced
this issue
May 13, 2024
In the UI, show a metric as needing a measurement because the source parameters were recently changed. Implemented by: - In the collector: adding a hash of the source parameters to measurements. - In the API-server: compare the hash of the latest measurement with the hash of the current configuration when adding recent measurements to a report and mark the metric as outdated. - In the UI: show metrics as needing a measurement if the last measurement is outdated. Open issues: - Seeing the source parameter hash is only useful in the most recent measurement, should the hash be removed from the latest measurement before inserting a new one? Closes #3134.
fniessink
added a commit
that referenced
this issue
May 13, 2024
In the UI, show a metric as needing a measurement because the source parameters were recently changed. Implemented by: - In the collector: adding a hash of the source parameters to measurements. - In the API-server: compare the hash of the latest measurement with the hash of the current configuration when adding recent measurements to a report and mark the metric as outdated. - In the UI: show metrics as needing a measurement if the last measurement is outdated. Open issues: - Seeing the source parameter hash is only useful in the most recent measurement, should the hash be removed from the latest measurement before inserting a new one? Closes #3134.
fniessink
added a commit
that referenced
this issue
May 14, 2024
In the UI, show a metric as needing a measurement because the source parameters were recently changed. Implemented by: - In the collector: adding a hash of the source parameters to measurements. - In the API-server: compare the hash of the latest measurement with the hash of the current configuration when adding recent measurements to a report and mark the metric as outdated. - In the UI: show metrics as needing a measurement if the last measurement is outdated. Open issues: - Seeing the source parameter hash is only useful in the most recent measurement, should the hash be removed from the latest measurement before inserting a new one? Closes #3134.
fniessink
added a commit
that referenced
this issue
May 14, 2024
In the UI, show a metric as needing a measurement because the source parameters were recently changed. Implemented by: - In the collector: adding a hash of the source parameters to measurements. - In the API-server: compare the hash of the latest measurement with the hash of the current configuration when adding recent measurements to a report and mark the metric as outdated. - In the UI: show metrics as needing a measurement if the last measurement is outdated. Open issues: - Seeing the source parameter hash is only useful in the most recent measurement, should the hash be removed from the latest measurement before inserting a new one? Closes #3134.
fniessink
added a commit
that referenced
this issue
May 14, 2024
In the UI, show a metric as needing a measurement because the source parameters were recently changed. Implemented by: - In the collector: adding a hash of the source parameters to measurements. - In the API-server: compare the hash of the latest measurement with the hash of the current configuration when adding recent measurements to a report and mark the metric as outdated. - In the UI: show metrics as needing a measurement if the last measurement is outdated. Open issues: - Seeing the source parameter hash is only useful in the most recent measurement, should the hash be removed from the latest measurement before inserting a new one? Closes #3134.
fniessink
added a commit
that referenced
this issue
May 14, 2024
In the UI, show a metric as needing a measurement because the source parameters were recently changed. Implemented by: - In the collector: adding a hash of the source parameters to measurements. - In the API-server: compare the hash of the latest measurement with the hash of the current configuration when adding recent measurements to a report and mark the metric as outdated. - In the UI: show metrics as needing a measurement if the last measurement is outdated. Open issues: - Seeing the source parameter hash is only useful in the most recent measurement, should the hash be removed from the latest measurement before inserting a new one? Closes #3134.
fniessink
added a commit
that referenced
this issue
May 14, 2024
In the UI, show a metric as needing a measurement because the source parameters were recently changed. Implemented by: - In the collector: adding a hash of the source parameters to measurements. - In the API-server: compare the hash of the latest measurement with the hash of the current configuration when adding recent measurements to a report and mark the metric as outdated. - In the UI: show metrics as needing a measurement if the last measurement is outdated. Open issues: - Seeing the source parameter hash is only useful in the most recent measurement, should the hash be removed from the latest measurement before inserting a new one? Closes #3134.
fniessink
added a commit
that referenced
this issue
May 15, 2024
In the UI, show a metric as needing a measurement because the source parameters were recently changed. Implemented by: - In the collector: adding a hash of the source parameters to new measurements (and removing it from old measurements). - In the API-server: compare the hash of the latest measurement with the hash of the current configuration when adding recent measurements to a report and mark the metric as outdated. - In the UI: show metrics as needing a measurement if the last measurement is outdated. Closes #3134.
fniessink
added a commit
that referenced
this issue
May 15, 2024
In the UI, show a metric as needing a measurement because the source parameters were recently changed. Implemented by: - In the collector: adding a hash of the source parameters to new measurements (and removing it from old measurements). - In the API-server: compare the hash of the latest measurement with the hash of the current configuration when adding recent measurements to a report and mark the metric as outdated. - In the UI: show metrics as needing a measurement if the last measurement is outdated. Closes #3134.
fniessink
added a commit
that referenced
this issue
May 16, 2024
In the UI, show a metric as needing a measurement because the source parameters were recently changed. Implemented by: - In the collector: adding a hash of the source parameters to new measurements (and removing it from old measurements). - In the API-server: compare the hash of the latest measurement with the hash of the current configuration when adding recent measurements to a report and mark the metric as outdated. - In the UI: show metrics as needing a measurement if the last measurement is outdated. Closes #3134.
fniessink
added a commit
that referenced
this issue
May 16, 2024
In the UI, show a metric as needing a measurement because the source parameters were recently changed. Implemented by: - In the collector: adding a hash of the source parameters to new measurements (and removing it from old measurements). - In the API-server: compare the hash of the latest measurement with the hash of the current configuration when adding recent measurements to a report and mark the metric as outdated. - In the UI: show metrics as needing a measurement if the last measurement is outdated. Closes #3134.
fniessink
added a commit
that referenced
this issue
May 22, 2024
fniessink
added a commit
that referenced
this issue
May 22, 2024
fniessink
added a commit
that referenced
this issue
May 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When the source(s) of a metric have been changed, but the new measurement is not available yet:
hourglass
icon to the measurement"The source configuration of this metric has been changed.
Collecting the new measurement data may take a few moments.
The metric was last measured 2 minutes ago (23-12-2023 13:10)
The configurations updated 20 seconds ago (22-12-2023 09:58)"
How to determine whether the metric was measured after it was edited? Add timestamps to metrics and sources in the report when they are changed. Compare the timestamps with the end of the most recent measurement.
The text was updated successfully, but these errors were encountered: