Feature #75
Syslog compliant logs
| Status: | Closed | Start date: | 2010-01-11 | ||
|---|---|---|---|---|---|
| Priority: | Normal | Due date: | |||
| Assignee: | Ismael Marín Carrión | % Done: | 90% |
||
| Category: | - | ||||
| Target version: | 5.8 |
Description
Hello Gridway Team
usually every mature software on Linux offers the opportunity to write logs in the Syslog format, at least considering the /usr/bin/logger binary and offering some place/way to configure the facility and priority of the log emitted; this allow to the System Administrator to store the logs in a central point, possibly using also a DB and a visualization tool to browse and search important events occurred during the time.
Just to show a concrete example, my personal choice, so far, is a centralized logging system based on rsyslog and MySQL http://www.rsyslog.com/ and the tool phplogcon http://www.phplogcon.com/ but there are several choices on the market.
Also, Syslog compliant logs are important to write own rules for Realtime Logs Analysis tools like OSSEC http://www.ossec.net/ and receive alerts by e-mail when Gridway can't work properly.
thanks for your attention,
good work
Fabio Martinelli
Associated revisions
Feature #75: Syslog compliant logs
History
Updated by Fabio Martinelli about 2 years ago
this is not a bug, it's a feature request
Updated by Alejandro Lorca about 2 years ago
- Tracker changed from Bug to Feature
Updated by Eduardo Huedo about 1 year ago
- Assignee set to Ismael Marín Carrión
- Target version set to 5.7
- Estimated time set to 15.00
Updated by Eduardo Huedo about 1 year ago
- Status changed from New to Assigned
Updated by Eduardo Huedo 11 months ago
- Target version changed from 5.7 to 5.8
Updated by Eduardo Huedo 8 months ago
- % Done changed from 0 to 90
Updated by Eduardo Huedo 8 months ago
- Estimated time deleted (
15.00)
Updated by Eduardo Huedo 7 months ago
- Status changed from Assigned to Resolved
Updated by Eduardo Huedo 4 months ago
- Status changed from Resolved to Closed