Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

default behavior of dd_message_key from out_datadog is broken #8982

Open
pmeier opened this issue Jun 19, 2024 · 2 comments
Open

default behavior of dd_message_key from out_datadog is broken #8982

pmeier opened this issue Jun 19, 2024 · 2 comments

Comments

@pmeier
Copy link
Contributor

pmeier commented Jun 19, 2024

Bug Report

Documentation states

{
FLB_CONFIG_MAP_STR, "dd_message_key", NULL,
0, FLB_TRUE, offsetof(struct flb_out_datadog, dd_message_key),
"By default, the plugin searches for the key 'log' "
"and remap the value to the key 'message'. "
"If the property is set, the plugin will search the property name key."
},

But the default behavior is not happening. If you leave this configuration option out, no processing is applied and thus by default the 'log' instead of the 'message' key is used. And since this format is not recognized by Datadog, the message does not show up at all.

We figured this out by configuring the plugin to send its data to a self-controlled HTTP server that does nothing but mirror back its input.

Expected behavior

Honor the default behavior described in the documentation.

Your Environment

  • Version used: 3.0.7
  • Environment name and version (e.g. Kubernetes? What version?): Kubernetes
  • Filters and plugins: out_datadog
@patrick-stephens
Copy link
Contributor

Please can you follow the issue template to capture all the relevant information like OS, target, what version of Fluent Bit, etc.?

@pmeier
Copy link
Contributor Author

pmeier commented Jun 25, 2024

Done @patrick-stephens

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants