[
https://issues.apache.org/jira/browse/CASSANDRA-17948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17613745#comment-17613745
]
Stefan Miklosovic commented on CASSANDRA-17948:
-----------------------------------------------
btw, in practice, ThresholdFilter would be set at least to WARN, I do not think
there is a lot of added value to go through INFO logs, why would you? There is
other telemetry for that, diagnostic events, jmx metrics ... but WARN or ERROR
would be nice to see for sure. So there will not be a lot of WARNs or ERRORs in
runtime, a magnitude less than INFO. It would take quite a buggy node to fill
that buffer with WARN or ERROR only.
> Get warning and errors through virtual tables
> ---------------------------------------------
>
> Key: CASSANDRA-17948
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17948
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Michiel Saelen
> Priority: Normal
>
> The warnings and errors are currently only accessible through Cassandra logs.
> Automating the monitoring of the nodes would be much easier/secure if we can
> make use of virtual tables to get the logs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
