Skip to content
This repository has been archived by the owner on Sep 8, 2018. It is now read-only.

Tag or label feature #33

Closed
nooproblem opened this issue Jan 26, 2017 · 2 comments
Closed

Tag or label feature #33

nooproblem opened this issue Jan 26, 2017 · 2 comments

Comments

@nooproblem
Copy link

nooproblem commented Jan 26, 2017

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. 👍

@peterbourgon
Copy link
Member

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!

@peterbourgon
Copy link
Member

peterbourgon commented Jan 27, 2017

Taken from another comment — I'd be happy to add basic annotation to oklog forward . . . What do you think of a repeatable flag, like

myservice | oklog forward -prefix $(hostname) -prefix $MY_ENV_VAR ...

Creating log lines like

nydata03a MYVALUE 2016-01-26 12:34:56 [DEBUG] reticulating splines...

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

No branches or pull requests

2 participants