You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been reviewing the telemetry for the Benthos pipeline as described here, but I was unable to find a way to extract custom attributes.
For example, I have a configuration similar to the one shown below. From my understanding, under the hood, payload.go is responsible for extracting the configuration and presenting it in the telemetry data.
Currently, the telemetry output only includes the following attributes:
name: output_pipeline_name
name: output_cloud_storage
However, I would like to extract additional details from the pipeline_name section, such as dsn , max_in_flight, and organize them under a separate custom attribute.
My goal is to ensure that these attributes are explicitly available in the telemetry data for easier monitoring and debugging. Is there a recommended approach to achieve this? If Redpanda's telemetry pipeline does not support custom attributes by default, are there any workarounds, such as modifying the payload.go implementation or using an alternative configuration method?
Any guidance or best practices on this would be greatly appreciated!
Hi All
I have been reviewing the telemetry for the Benthos pipeline as described here, but I was unable to find a way to extract custom attributes.
For example, I have a configuration similar to the one shown below. From my understanding, under the hood, payload.go is responsible for extracting the configuration and presenting it in the telemetry data.
Currently, the telemetry output only includes the following attributes:
However, I would like to extract additional details from the
pipeline_name
section, such asdsn
,max_in_flight
, and organize them under a separate custom attribute.My goal is to ensure that these attributes are explicitly available in the telemetry data for easier monitoring and debugging. Is there a recommended approach to achieve this? If Redpanda's telemetry pipeline does not support custom attributes by default, are there any workarounds, such as modifying the payload.go implementation or using an alternative configuration method?
Any guidance or best practices on this would be greatly appreciated!
And here is the trace configuration
The text was updated successfully, but these errors were encountered: