[
https://issues.apache.org/jira/browse/CASSANDRA-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012661#comment-13012661
]
Jonathan Ellis commented on CASSANDRA-2281:
-------------------------------------------
bq. Also you could add a log4j socket appender for error level that would
collect the actual errors for operators to be notified of. Another option would
be to write a log4j FileAppender that also has a JMX bean.
Well, you can specify multiple appenders, so all you really need is to stack
the JMX one in w/ the existing RollingFileAppender.
Looks like JBoss had the same idea:
http://community.jboss.org/wiki/JMXNotificationAppender
> keep a count of errors
> ----------------------
>
> Key: CASSANDRA-2281
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2281
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Ryan King
> Assignee: Ryan King
> Priority: Minor
> Fix For: 0.7.5
>
> Attachments: patch, textmate stdin Vrj9Xa.txt
>
>
> I have patch that keeps a counter (exposed via jmx) of errors. This is quite
> useful for operators to keep track of the quality of cassandra without having
> to tail and parse logs across a cluster.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
