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

[Request]: Filter your Host by Services #3480

Closed
roshan-elastic opened this issue Dec 21, 2023 · 0 comments · Fixed by #3517
Closed

[Request]: Filter your Host by Services #3480

roshan-elastic opened this issue Dec 21, 2023 · 0 comments · Fixed by #3517

Comments

@roshan-elastic
Copy link
Contributor

Description

We have added a improvement to allow users to quickly filter their hosts by the service running on them.

This helps users who are investigating a service (or a host that a service is running on) compare different hosts to see if the problem lies with the service or the host.

Screenshot - see **Service Name** drop-down
image

Notes

  • Right now, we will only show the services which are instrumented with APM (and this is mentioned in the popver):
image
  • As with the other drop-downs, the values are sorted by 'document count'. This is unlikely to mean much to the end user but it is effectively the count of events received by Elastic for the hosts that are running that service - we may want to mention what the 'document count' means.

Note : We acknowledge this is probably confusing and we're seeing if we can change this to show the host count instead (in the future)

Resources

Tag Line

Here is how we're describing it:

"Easily filter down to the hosts that your service is running on so you can more easily identify resource constraints, compare behavior across different host and identify the root causes for incidents quicker"

Link in UI

See it running on edge:

link

Which documentation set does this change impact?

Stateful and Serverless

Feature differences

Same across both

What release is this request related to?

8.12

Collaboration model

The documentation team

Point of contact.

Main contact: @roshan-elastic

Stakeholders: @smith @neptunian

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants