The filter on apm ui did not work

[wajika]

ELK version: 7.8.0

I have 2 questions

1.the filter on apm ui did not work

See gif picture for details
https://drive.google.com/file/d/15kZ7qVO4rKI29kUXJSsnLLs4FZUvFhTP/view?usp=sharing

2.How is transaction interface information and error message related to each other? Similar to using actions to jump

It seems that only these (container id...) can be used to filter, but the operation is not very convenient.

Can't see the error message corresponding to transaction quickly

[dgieselaar (Dario Gieselaar)]

Hello @wajika! I'm not sure I entirely understand your question.

• Re #1, I cannot open the link you've provided. Also, can you clarify what your expectations are (re: "it did not work")?
• Re #2, can you clarify? Do you mean that you'd like to have a link for all errors related to a transaction?

[wajika]

@dgieselaar

I've shared the file again. I don't know if you can see the picture.
https://ac-data.info/d/X0aLj35itFM

SendGB | Send Large Files | Free file sharing

For #1
I chose to view only the content of http4XX,but the information displayed is http200.

For #2
We usually go to the transaction page to find the request method, but this page does not have error information, and the error page does not display the request method name. There is no association between the two and it is very troublesome to use

transaction page has no error content

The error page has "error" content, but the request method is not displayed directly

[dgieselaar (Dario Gieselaar)]

For #1, what I think is happening is that the trace sample is not updated. The rest of the data should reflect the filters you have chosen. We have an open issue for this in the backlog: https://github.com/elastic/kibana/issues/67744.

For #2, you can click through to the related errors. You can click on the square on the timeline, or on "1 error" after the transaction name. Would that help? You can also use the query bar in the errors view to search for certain errors, e.g. by specifying "request.method:GET".

[wajika]

For #1
if it is an unresolved bug, then I will leave it alone for now.

For #2
Too many operations will bring a certain learning cost, I think the simpler the operation, the better.
But this depends on the judgment of the elastic team.

[wajika]

In another case, if the error page contains a lot of content, how can I find the error content corresponding to the request method in the transaction page?
@dgieselaar

[dgieselaar (Dario Gieselaar)]

@wajika what do you mean with content? And "content corresponding to the request method"?

[wajika]

For example, if I am looking for POST CallCenter/InCall information, I can find it when I enter the transaction page. If I want to find error information, the interface information is not displayed on the error page.

If there are many errors on the error page, it is difficult to quickly find the information generated by POST CallCenter/InCall.

[wajika]

I found a way to set a custom link in transaction actions, but there is no associated field between transaction and error data