|
|
| Subject: | Colon : in syslog message split the message content and add to component column |
| Author: | [Not Specified] |
| Posted: | 2014-10-21 04:47 |
Similar to the post at http://community.zenoss.org/message/64195 , when we send the syslog contains colon, take below message as example
Error message: failed to start up service
Message will be split by colon. "Error message" will be put into Component column in Zenoss, and message body will be "failed to start up service"
But if removed the colon ":" from error message
Error mesage failed to start up service
What I received in Zenoss will be "computername.corp.kira.com GenericLog 0 Error message failed to start up service"
I tried to filter it by transform in Events Classes page, it does not work. Seems the colon ":" used by Zenoss before any transform we can setup in Event Class page.
Thanks for help~
| Subject: | Anyone knows if it is a bug? |
| Author: | [Not Specified] |
| Posted: | 2014-10-21 22:37 |
Anyone knows if it is a bug The problem was not fixed in the old post . http://community.zenoss.org/message/64195
| Subject: | any body can help? |
| Author: | [Not Specified] |
| Posted: | 2014-10-24 04:43 |
any body can help
| Subject: | Can anybody check and help ? |
| Author: | [Not Specified] |
| Posted: | 2014-11-14 01:08 |
Can anybody check and help
| Subject: | How to change Zenoss behavior |
| Author: | [Not Specified] |
| Posted: | 2014-11-14 01:10 |
How to change Zenoss behavior , not to split the syslog by colon How to change the setting
| Subject: | anybody can help? |
| Author: | [Not Specified] |
| Posted: | 2014-12-24 19:49 |
anybody can help
| Subject: | This appears to be a bug. |
| Author: | Andrew Kirch |
| Posted: | 2014-12-29 14:51 |
This appears to be a bug. File it as a P2 because it can cause loss of monitoring. I apologize that I didn't see this thread for so long. Thank you for bumping it! http://jira.zenoss.com is the bug tracker.
Andrew Kirch
akirch@gvit.com
Need Zenoss support, consulting or custom development Look no further. Email or PM me!
Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard
| Subject: | Hi Trelane |
| Author: | [Not Specified] |
| Posted: | 2015-01-05 02:48 |
Hi Trelane
At the present , do you know if any work around can help Can you give us some info how and when Zenoss split these syslog message body before it can be handled by Zenserverevent deamon
| Subject: | The only solution I can think |
| Author: | Andrew Kirch |
| Posted: | 2015-01-05 09:24 |
The only solution I can think of would be to run a regexp against the log in crontab to replace : with something else.
Andrew Kirch
akirch@gvit.com
Need Zenoss support, consulting or custom development Look no further. Email or PM me!
Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard
| Subject: | Hi Andrew Kirch, is the bug |
| Author: | [Not Specified] |
| Posted: | 2015-06-24 00:57 |
Hi Andrew Kirch, is the bug fixed Which version of Zenoss core has the bug fixed Thanks
| Subject: | is the bug fixed? Which |
| Author: | [Not Specified] |
| Posted: | 2015-08-20 01:18 |
is the bug fixed Which version of Zenoss core has the bug fixed Thanks
| Subject: | The bug is fixed in: |
| Author: | Andrew Kirch |
| Posted: | 2015-08-24 14:14 |
The bug is fixed in:
Zenoss 4.2.5.SP378
and
Zenoss 5.0.1
Andrew Kirch
akirch@gvit.com
Need Zenoss support, consulting or custom development Look no further. Email or PM me!
Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard
| < |
Previous Trigger dependencies broken |
Next funky Filesystem display confusing parser |
> |