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
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.
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)?
The text was updated successfully, but these errors were encountered:
This is the setup I have:
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:
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)?
The text was updated successfully, but these errors were encountered: