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
Seems like when setting TAGS env variable, messages will still have a rkubelog tag, but custom tags are added at json.rkubelog.tag attribute of the message . I think expected behaviour in this case should be that these tags are not added to json, but set on a message (in loggly endpoint url: https://logs-01.loggly.com/inputs/%TOKEN%/tag/%TAGS%, while now everything gets sent to https://logs-01.loggly.com/inputs/%TOKEN%/tag/rkubelog)
The text was updated successfully, but these errors were encountered:
Related to #15
Seems like when setting
TAGS
env variable, messages will still have arkubelog
tag, but custom tags are added atjson.rkubelog.tag
attribute of the message . I think expected behaviour in this case should be that these tags are not added to json, but set on a message (in loggly endpoint url:https://logs-01.loggly.com/inputs/%TOKEN%/tag/%TAGS%
, while now everything gets sent tohttps://logs-01.loggly.com/inputs/%TOKEN%/tag/rkubelog
)The text was updated successfully, but these errors were encountered: