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
Is your feature request related to a problem? Please describe.
Similar to datadogexporter's hostmetadata intake, the AWS X-Ray API has PutTelemetryRecords which can be used to collect simple telemetry on the behavior of X-Ray exporting mechanisms. This is currently unsupported in the awsxrayexporter.
Describe the solution you'd like
The TelemetryRecords collect segment received/rejected/sent counts and PutTraceSegment error counts. So, the collection mechanism needs to be shared between the receiver and the exporter.
One option is to create a telemetry collector in internal/aws/xray that can be initialized and managed by the exporter and accessible by the receiver for reporting.
The configuration should make the telemetry opt-in and easy to configure. It should be included in the exporter config.
typeTelemetryConfigstruct {
// Enabled determines whether any telemetry should be recorded.Enabledbool`mapstructure:"enabled"`// IncludeMetadata determines whether metadata (instance ID, hostname, resourceARN)// should be included in the telemetry.IncludeMetadatabool`mapstructure:"include_metadata"`
}
Describe alternatives you've considered
This could also be done with an extension and would not be as simple to configure. The telemetry could also be opt-out.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Component(s)
exporter/awsxray, receiver/awsxray
Is your feature request related to a problem? Please describe.
Similar to
datadogexporter
's hostmetadata intake, the AWS X-Ray API has PutTelemetryRecords which can be used to collect simple telemetry on the behavior of X-Ray exporting mechanisms. This is currently unsupported in theawsxrayexporter
.Describe the solution you'd like
The
TelemetryRecords
collect segment received/rejected/sent counts and PutTraceSegment error counts. So, the collection mechanism needs to be shared between the receiver and the exporter.One option is to create a telemetry collector in
internal/aws/xray
that can be initialized and managed by the exporter and accessible by the receiver for reporting.The configuration should make the telemetry opt-in and easy to configure. It should be included in the exporter config.
Describe alternatives you've considered
This could also be done with an extension and would not be as simple to configure. The telemetry could also be opt-out.
Additional context
No response
The text was updated successfully, but these errors were encountered: