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

How to send already tagged data? #4

Open
rakeshrm opened this issue Mar 21, 2022 · 0 comments
Open

How to send already tagged data? #4

rakeshrm opened this issue Mar 21, 2022 · 0 comments

Comments

@rakeshrm
Copy link

This is the setup I have:

  • source is generating data in syslog - the data is already tagged (e.g. my.app.event.sample) at the source
  • we have a fluentd installation that receives this syslog evente (in_syslog) plugin
  • we need to send this data to Devo

The config and communication are all working, we can see the data in Devo (in the unknown.unknown table).

The problem is: the in_syslog plugin forces us to create a tag, in order to do proper routing. The out_devo plugin is using this tag to tag the data it is sending to Devo.

e.g. if I define my source and match as:

<source>
    @type syslog
    port 5140
    bind 0.0.0.0
    <transport tcp>
    </transport>
    tag mylogs
</source>

<match mylogs.**>
  @type devo
  host eu.elb.relay.logtrust.net
  port 443
  ca_cert <>
  client_cert <>
  client_key <>
  verify_cert_name false
  <format>
    @type single_value
    message_key message
  </format>
</store>

The data I receive at Devo is always tagges as mylogs.user.notice, and hence ends up in unknown.uknown

The incoming data is already tagged with the proper Devo tag (each event could have a different Devo tag)
How do I ensure that the tag in the incoming syslog is used in the output as well (and NOT the tag used for routing)?

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

No branches or pull requests

1 participant