Bug 887924 - Logging to syslog.
Summary: Logging to syslog.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: logging
Version: mainline
Hardware: All
OS: All
medium
medium
Target Milestone: ---
Assignee: Raghavendra Talur
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-17 15:54 UTC by Jiri Hoogeveen
Modified: 2013-07-24 17:44 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 17:44:32 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Jiri Hoogeveen 2012-12-17 15:54:46 UTC
Hi,

We are running 10 servers with glusterfs on it. To form 1 big file systeem.
This works great, but I have only 1 issue, Logs.

We use a central syslog server, which recieves all logs of our servers. This is nice to view.manage and monitor logs.

Only for glusterfs I have to log in ever servers, to view logs, and I have to run on every server a nagios plugin, to watches the logs of glusterfs.

It would be really nice, if glusterfs can log all messages to syslog. So I can watch my logs and monitor them from 1 place.

I know, I can make a script or use a external program, to parse the logs and send the logs to syslog. But I think this function should be in glusterfs.

Grtz, Jiri

Comment 1 Amar Tumballi 2012-12-18 10:03:54 UTC
can you try 'gluster volume set <VOL> diagnostics.brick-sys-log-level WARNING" ?

Comment 2 Jiri Hoogeveen 2012-12-18 10:24:24 UTC
@Amar, thnx this works.

I guess, when I set this 'gluster volume set <VOL> diagnostics.brick-sys-log-level WARNING" I get the warnings, errors and critical messages?

But what about the info messages?

Comment 3 Amar Tumballi 2012-12-18 11:57:04 UTC
(In reply to comment #2)
> @Amar, thnx this works.
> 

Thanks for confirming.

> I guess, when I set this 'gluster volume set <VOL>
> diagnostics.brick-sys-log-level WARNING" I get the warnings, errors and
> critical messages?

Yes, thats right.

> 
> But what about the info messages?

You can give 'INFO' instead of 'WARNING' in the above message. Please check the 'gluster volume set help' :-)

Let us know if this info works for you, can we go ahead and close the bug?

Comment 4 Jiri Hoogeveen 2012-12-18 12:11:45 UTC
Nop, I can not set INFO.

root@gluster-brick-01n1:~# gluster volume set glusterfsvol02 diagnostics.client-sys-log-level INFO
option sys-log-level INFO: 'INFO' is not valid (possible options are WARNING, ERROR, CRITICAL.)
Set volume unsuccessful


btw, I'm using glusterfs 3.3.1

Comment 5 Vijay Bellur 2013-02-11 16:43:34 UTC
CHANGE: http://review.gluster.org/4499 (Debug/io-stats: Enable INFO level in syslog) merged in master by Vijay Bellur (vbellur)

Comment 6 Jiri Hoogeveen 2013-02-14 09:13:48 UTC
Create to see, that INFO is added :)

But after seeing the code, I have 1 question.

Why not include every message type?

for syslog
.value = { "WARNING", "ERROR", "INFO", "CRITICAL"}

for brick-log-level
.value = { "DEBUG", "WARNING", "ERROR", "INFO","CRITICAL", "NONE", "TRACE"}

Comment 7 Amar Tumballi 2013-02-14 11:05:59 UTC
DEBUG, TRACE levels are very much a glusterfs debug levels, and *should* not be used in a 'admin' setup. That is the reason for not having these options for syslog.

Comment 8 Jiri Hoogeveen 2013-02-14 11:34:41 UTC
Ok, that is clear. Thanks for explaning it.


Note You need to log in before you can comment on or make changes to this bug.