-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[InfraUI] Allow users to filter by service.name #40424
Comments
Pinging @elastic/infra-logs-ui |
IIRC we add them to the composite query to be able to use them for displaying the nodes. According to https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-bucket-composite-aggregation.html we should be able to set |
will retest once #40804 is in |
having Infra UI automatically query APM indices relates to ensure index patterns are defined in the same place: #41360 |
This work relies on: elastic/apm-server#2502 |
As elastic/apm-server#2540 got merged, what are the next steps for this one? |
@roncohen are there still any blockers? |
closing as the code has been massaged to allow for this use case. Will open separate discussion on what to do with the index patterns. |
We should make it possible to filter the InfraUI view to show hosts/pods/containers that are serving a specific APM service. You can imagine linking directly from the APM UI service list to the infra UI to see the an overview of the infrastructure that currently deals with this service.
I did a preliminary investigation and the good news is that it almost works. APM sends up data that includes
service.name
,host.name
,container.id
, andkubernetes.pod.id
where available. There are 3 outstanding issues:host.hostname
while infra expectshost.name
. By setting up an ingest pipeline that just copies the value for APM data i got it to work for the "host" page. I'll talk to ECS folks and APM folks separately to see what we do about it.host.name
,container.name
etc. in the composite grouping key. The APM documents do not havecontainer.name
while the metricbeat documents havecontainer.name
and so when we try to merge buckets it does not work because the keys don't match up. I wonder if there's a reason we use the names in additions to the IDs in the grouping or if it's a leftover from [InfraUI] Use container IDs instead of names for grouping, filtering and linking #26359apm-*
or similar to the defaultThe text was updated successfully, but these errors were encountered: