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

Process tab in Host monitoring seems to be confusing users, report N/A when data exists #181914

Open
fearful-symmetry opened this issue Apr 26, 2024 · 6 comments
Labels
bug Fixes for quality problems that affect the customer experience Feature:ObsHosts Hosts feature within Observability needs-refinement A reason and acceptance criteria need to be defined for this issue Team:obs-ux-infra_services Observability Infrastructure & Services User Experience Team

Comments

@fearful-symmetry
Copy link

So, the the Process tab in host monitoring presents a summary of process state at the top:

image

It appears that this UI has spawned an entire issue from users who are concerned that something in beats is broken: elastic/beats#38120

The problem is that on most linux systems, the majority of processes will report as a sleep state unless are under heavy CPU load. Users who aren't experienced with linux process scheduling, see something counter-intuitive like "everything on the host is sleeping" and assume there's a problem.

There's also an adjacent problem, demonstrated in the screenshot, where the process states show N/A despite the process list showing a number of running processes.

I'm not sure what to do here. Part of me thinks we should just remove the process state summary element at the top, as for most use cases, counts of running processes aren't particularly helpful. We could also replace it with a count of total processes, or provide some kind of tooltip.

@fearful-symmetry fearful-symmetry added bug Fixes for quality problems that affect the customer experience Team:obs-ux-infra_services Observability Infrastructure & Services User Experience Team labels Apr 26, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services)

@smith smith added needs-refinement A reason and acceptance criteria need to be defined for this issue Feature:ObsHosts Hosts feature within Observability labels Apr 26, 2024
@crespocarlos
Copy link
Contributor

There's also an adjacent problem, demonstrated in the screenshot, where the process states show N/A despite the process list showing a number of running processes.

@fearful-symmetry , the reason for that is because the process_summary metricset needs to be enabled in the system module integration. Perhaps we could replace the need for that metricset by using the information provided on the list, but I'm not sure if we'll have all the information that the summary shows.

@fearful-symmetry
Copy link
Author

fearful-symmetry commented Apr 29, 2024

@crespocarlos yeah, the link between that particular visualization and the process_summary metricset is a bit non-obvious, even I assumed it was just aggregating the data from the below list. The same data is present a few inches away, so it makes it look like a bug.

@roshan-elastic
Copy link

Hey @fearful-symmetry - following on from my previous comment (on the related issue)...would it help to have a call to talk this through?

@fearful-symmetry
Copy link
Author

@roshan-elastic I wouldn't be opposed to that, but be warned, I have a lot of strong opinions about system metrics UX ;)

@roshan-elastic
Copy link

Thanks @fearful-symmetry

I don't have strong opinions at this stage :)

I'll set something up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:ObsHosts Hosts feature within Observability needs-refinement A reason and acceptance criteria need to be defined for this issue Team:obs-ux-infra_services Observability Infrastructure & Services User Experience Team
Projects
None yet
Development

No branches or pull requests

5 participants