[Filebeat] httpjson tracer logs doesn't include chain request/response

[kcreddy]

When chain requests are being made using httpjson input, the tracer logs captured via request.tracer.filename flag doesn't include chain requests or responses. They only show parent request and response, which doesn't show the full picture.

[elasticmachine]

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

[kcreddy]

As described in #37551 (comment), if each chain requests/responses can be captured independently within their step config, then this issue will be redundant.

Need to decide the right approach. I think #37551 might be better approach after the httpjson docs are also updated stating that chain request/response can also be traced.

[kcreddy]

Here is the SDH too - 4177

With regards to this SDH, the Tenable PR elastic/integrations#8831 that allows capturing chain requests/responses within each step config is now merged. Tenable integration version 2.8.0 should have the chain request/responses added to the agent diagnostics.

[elasticmachine]

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

[efd6]

@kcreddy I think #37682 should have closed this. Am I missing something?

[kcreddy]

I think #37682 should have closed this. Am I missing something?

Yes, it should be closed.