-
Notifications
You must be signed in to change notification settings - Fork 456
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
[System] Replace TSVB gauges in system metrics and host overview dashboards #4975
Conversation
💔 Build Failed
Expand to view the summary
Build stats
Steps errorsExpand to view the steps failures
|
🌐 Coverage report
|
failure may relate to #4950 |
…pdate-metric-overview-dashboards
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall looks good, just some questions on the queries, especially "NOT system.network.name : l*"
@@ -8,7 +8,7 @@ | |||
"highlightAll": true, | |||
"query": { | |||
"language": "kuery", | |||
"query": "" | |||
"query": "host.name:\"docker-fleet-agent\"" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this supposed to be here? I don't think this dashboard is limited to docker-fleet-agent
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gvnmagni : do you have any comment on this feedback? Could this be something that snuck in while we were trying things out?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
honestly, I don't know. When we updated these visualizations we tried to replicate what was happening with the previous version of them and given my lack of competences on how data is structured behind these chart I had to intensively rely for help on Joe Reuter, who I believe originally made those. So sometimes I just followed instructions and I can't actually remember if these queries came from him or this is just an error (which would be weird, I have been very careful in not creating anything that could be unexpected).
Same happens for the next comments, the ones related to the "NOT system.network.name" query. Is it possible that is was made to avoid having dirty data of some sort? What does happen to the values if we remove these queries?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense, @gvnmagni ! Don't worry, I will evaluate the queries here and address this feedback. Thanks for your help. 🙏
"internalReferences": [], | ||
"query": { | ||
"language": "kuery", | ||
"query": "NOT system.network.name : l*" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what is this query for?
"language": "kuery", | ||
"query": "data_stream.dataset : \"system.network\"" | ||
"query": "NOT system.network.name : l*" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what is this query for?
"internalReferences": [], | ||
"query": { | ||
"language": "kuery", | ||
"query": "NOT system.network.name : l*" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and this query?
"internalReferences": [], | ||
"query": { | ||
"language": "kuery", | ||
"query": "NOT system.network.name : l*" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same here
"language": "kuery", | ||
"query": "data_stream.dataset : \"system.memory\"" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we still want this query?
"language": "kuery", | ||
"query": "data_stream.dataset : \"system.cpu\"" | ||
"query": "" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we still want this query?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is key that we prefilter on dataset. Same above.
@joshdover this PR currently changes nothing about how these metrics are computed. They will still suffer from #1437. I would like to use this as an opportunity to choose one of the more consistent strategies I mentioned here. That will reduce user confusion in the long run. How do I get an answer as to which strategy makes sense? |
Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as |
Hi! This PR has been stale for a while and we're going to close it as part of our cleanup procedure. We appreciate your contribution and would like to apologize if we have not been able to review it, due to the current heavy load of the team. Feel free to re-open this PR if you think it should stay open and is worth rebasing. Thank you for your contribution! |
…pdate-metric-overview-dashboards
Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as |
Hi! This PR has been stale for a while and we're going to close it as part of our cleanup procedure. We appreciate your contribution and would like to apologize if we have not been able to review it, due to the current heavy load of the team. Feel free to re-open this PR if you think it should stay open and is worth rebasing. Thank you for your contribution! |
Reopening as I'm not sure if these changes should still make it in. @joshdover |
Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as |
Closing in favor of #6743 |
What does this PR do?
System and host metric overview dashboards now use Lens metrics instead of TSVB gauges.
Checklist
changelog.yml
file.Related issues
Screenshots
Host overview
Before
After
System overview
Before
After