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
{{ message }}
This repository has been archived by the owner on Sep 8, 2018. It is now read-only.
Just wondering if there was any ideas on how distinguish between very similar logs that are pulled / pushed from multiple log endpoints? At the moment I am unable to find a way to distinguish between very similar logs, unless the log records happen to include something like a host name/IP, but then I could be missing something obvious. Is there any metadata added by the log forward feature? If not, might tags / labels added by the forward feature be a possible solution or would this be out of scope?
Thanks to Peter for the great idea and all the work so far. I am looking forward to see how oklog evolves in the future. 👍
The text was updated successfully, but these errors were encountered:
Annotations are totally supported, but should be done in your log pipeline, for example logstash. By the time OK Log is involved we treat all log records as opaque byte slices. Hope that helps!
Hi,
Just wondering if there was any ideas on how distinguish between very similar logs that are pulled / pushed from multiple log endpoints? At the moment I am unable to find a way to distinguish between very similar logs, unless the log records happen to include something like a host name/IP, but then I could be missing something obvious. Is there any metadata added by the log forward feature? If not, might tags / labels added by the forward feature be a possible solution or would this be out of scope?
Thanks to Peter for the great idea and all the work so far. I am looking forward to see how oklog evolves in the future. 👍
The text was updated successfully, but these errors were encountered: