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.
The current Datadog exporter implementation uses a hardcoded reporting period of 30 minutes for the host metadata reporter. While this interval might work for some environments, it is too long for scenarios where infrastructure changes need to be reflected promptly. Users have no control over this period, which can lead to delayed updates in Datadog’s infrastructure list and host map.
Describe the solution you'd like
I propose adding a configurable reporter_period parameter to the Datadog exporter’s host metadata configuration. This parameter would allow users to specify the frequency at which host metadata is sent to Datadog. By default, this value could remain at 30 minutes to ensure backward compatibility, but users would have the option to set it to shorter or longer intervals based on their needs.
For example, the configuration could look like this:
This change would involve updating the host metadata configuration structure, validating the parameter to ensure positive duration values, and passing it through to the metadata pusher and reporter logic (inframetadata).
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
- Introduced a `reporter_period` field in `HostMetadataConfig` to allow
customization of the metadata reporting interval.
- Default value set to 30 minutes for backward compatibility.
- Updated `pkg/datadog/config/host.go` to support the new
`reporter_period` field.
- Validated `reporter_period` in `pkg/datadog/config/config.go` to
ensure positive durations.
- Passed `reporter_period` to the metadata pusher in
`exporter/datadogexporter/internal/hostmetadata/config.go`.
- Modified `exporter/datadogexporter/hostmetadata.go` and `factory.go`
to integrate `reporter_period` into the reporter logic.
- Removed hardcoded constant for metadata reporting interval in favor of
the configurable value.
Fixesopen-telemetry#36450
Component(s)
exporter/datadog
Is your feature request related to a problem? Please describe.
The current Datadog exporter implementation uses a hardcoded reporting period of 30 minutes for the host metadata reporter. While this interval might work for some environments, it is too long for scenarios where infrastructure changes need to be reflected promptly. Users have no control over this period, which can lead to delayed updates in Datadog’s infrastructure list and host map.
Describe the solution you'd like
I propose adding a configurable
reporter_period
parameter to the Datadog exporter’s host metadata configuration. This parameter would allow users to specify the frequency at which host metadata is sent to Datadog. By default, this value could remain at 30 minutes to ensure backward compatibility, but users would have the option to set it to shorter or longer intervals based on their needs.For example, the configuration could look like this:
This change would involve updating the host metadata configuration structure, validating the parameter to ensure positive duration values, and passing it through to the metadata pusher and reporter logic (
inframetadata
).Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: