On Tue, Mar 12, 2013 at 3:08 PM, Olivier Hanesse
<olivier.hane...@gmail.com>wrote:
> Hello, [...]
> I think we should separate what I call "syslog" log with "Shinken internal
> logs"
>
> Maybe we could create a custom logging level and only this level will be
> stored into logstore ?
>
> What do you think about this ?
>
>
>
Olivier
>
> Hi,
Yes, such logs are not related. Some are internal to the Shinken program,
like a scheduler not reachable, or a bad configuration, and some are purely
logical, like a warning for a service (like a CPU service on a localhost
host). They should not go in the same filter from a LiveStatus point of
view.
The inner is an "alert" for Shinken, the other is a real "warning" from a
logical point of view, not the same thing at all. LiveStatus queries on
logs are mainly done for reporting (I'm not a fan of this, but whatever),
and inner logs (aka alerts) are not interested for reporting (if you want
to have the Shinken SLA, put a real host/service for it :) ).
So I'm for add a new "level" if need, and really separate theses logs in
the sqlite/mongodb databases, so the SLA queries will be fast (ok... not
too slow will be quite good...).
Jean
------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the
endpoint security space. For insight on selecting the right partner to
tackle endpoint security challenges, access the full report.
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
Shinken-devel mailing list
Shinken-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shinken-devel
