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

Show whether the latest measurement of metric has been done with the current configuration of its source(s) #3134

Closed
3 tasks done
Sebastiaan127001 opened this issue Dec 31, 2021 · 1 comment · Fixed by #8660
Assignees
Projects

Comments

@Sebastiaan127001
Copy link
Contributor

Sebastiaan127001 commented Dec 31, 2021

When the source(s) of a metric have been changed, but the new measurement is not available yet:

  • Add a hourglass icon to the measurement
  • Add a yellow label to the measurement
  • Add a warning popup:
    "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.

@fniessink fniessink changed the title FR show current activity to the user Show the user how long it will take until a metric will be measured and what the current status is Jan 5, 2022
@fniessink fniessink added the Feature New, enhanced, or removed feature label Jan 5, 2022
@fniessink fniessink added this to Backlog in Backlog via automation Jan 5, 2022
@fniessink fniessink moved this from Backlog to To be refined in Backlog Dec 23, 2022
@fniessink fniessink changed the title Show the user how long it will take until a metric will be measured and what the current status is Show the user how long it will take until a metric will be measured and allow for triggering a measurement Dec 23, 2022
@ICTU ICTU deleted a comment from Sebastiaan127001 Dec 23, 2022
@fniessink
Copy link
Member

Duplicates/overlaps #920.

@fniessink fniessink moved this from To be refined to Refinement agenda in Backlog Dec 21, 2023
@fniessink fniessink changed the title Show the user how long it will take until a metric will be measured and allow for triggering a measurement Show when a metric will be measured and whether a metric is currently being measured. Dec 21, 2023
@fniessink fniessink changed the title Show when a metric will be measured and whether a metric is currently being measured. Show whether the latest measurement of metric has been done with the current configuration of the metric Dec 28, 2023
@fniessink fniessink changed the title Show whether the latest measurement of metric has been done with the current configuration of the metric Show whether the latest measurement of metric has been done with the current configuration of metric and source(s) Dec 28, 2023
@fniessink fniessink changed the title Show whether the latest measurement of metric has been done with the current configuration of metric and source(s) Show whether the latest measurement of metric has been done with the current configuration of its source(s) Dec 28, 2023
@fniessink fniessink moved this from Refinement agenda to Ready in Backlog Dec 28, 2023
@fniessink fniessink added Usability and removed Feature New, enhanced, or removed feature labels Jan 25, 2024
@fniessink fniessink moved this from Ready to Development in progress (max 4) in Backlog May 8, 2024
@fniessink fniessink self-assigned this May 8, 2024
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 fniessink linked a pull request May 10, 2024 that will close this issue
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 fniessink moved this from Development in progress (max 4) to Reviewing in progress in Backlog May 15, 2024
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.
Backlog automation moved this from Reviewing in progress to Merged May 16, 2024
@fniessink fniessink moved this from Merged to Released in Backlog May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Backlog
Released
Development

Successfully merging a pull request may close this issue.

2 participants