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
We have a host with the DataDog agent installed and its config present. When sending an event to DataDog with this Python library, the event gets the tags from the config file attached. In our case this leads to duplicate tags which breaks some event queries in DataDog.
I've seen that this library accesses an agent config if present to get the host name. And indeed, setting attach_host_name=False when sending the event prevents this behavior. However, I've found no hint in the documentation that there is more than the host name taken from the config file, nor could I retrace this in the code, yet.
Looks like a bug to me or at least the option attach_host_name is misleading.
To Reproduce
Have a host with a datadog agent installed and tags defined in its config file.
Send an event to Datadog using this library without disabling attach_host_name.
The event has the tags from the agent's config file (in addition to any other tags that were specified to event, even duplicate tags)
Expected behavior
Sending an event (directly via DataDogs http API) should not interfere with a DataDog agent installed on that host except in the documented way, i.e. getting the host name.
Versions
datadog: 0.45.0
Python: 3.8
OS: RHEL 8
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had activity in the last 30 days. Note that the issue will not be automatically closed, but this notification will remind us to investigate why there's been inactivity. Thank you for participating in the Datadog open source community.
If you would like this issue to remain open:
Verify that you can still reproduce the issue in the latest version of this project.
Comment that the issue is still reproducible and include updated details requested in the issue template.
We have a host with the DataDog agent installed and its config present. When sending an event to DataDog with this Python library, the event gets the tags from the config file attached. In our case this leads to duplicate tags which breaks some event queries in DataDog.
I've seen that this library accesses an agent config if present to get the host name. And indeed, setting
attach_host_name=False
when sending the event prevents this behavior. However, I've found no hint in the documentation that there is more than the host name taken from the config file, nor could I retrace this in the code, yet.Looks like a bug to me or at least the option
attach_host_name
is misleading.To Reproduce
attach_host_name
.Expected behavior
Sending an event (directly via DataDogs http API) should not interfere with a DataDog agent installed on that host except in the documented way, i.e. getting the host name.
Versions
datadog: 0.45.0
Python: 3.8
OS: RHEL 8
The text was updated successfully, but these errors were encountered: