Ingest thread, task and processor IDs in Kafka

[kford-newrelic]

Description

For troubleshooting kafka related issues it is required to collect also thread-id, task-id and processor-node-id so that users can identify where an issue's rootcause lies.

On top of ingesting the data, users should be able to facet by thread-id, task-id and processor-node-id.

Acceptance Criteria

With a NRQL query, we are able to facet by thread, task and processor IDs

Design Consideration/Limitations

N/A

Dependencies

N/A

Additional context

N/A

[workato-integration[bot]]

https://issues.newrelic.com/browse/NR-159196

[kford-newrelic]

Consider for the oct-dec qtr but also consider below the cut-line

[kford-newrelic]

Assumed to be adding as attributes to events (not metrics).