[
https://issues.apache.org/jira/browse/CASSANDRA-17948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-17948:
------------------------------------------
Fix Version/s: 4.2
(was: 4.x)
Source Control Link:
https://github.com/apache/cassandra/commit/c08981888181392017761606f4490cca7f977db9
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
I run additional builds here in circleci
repeated utest
https://app.circleci.com/pipelines/github/instaclustr/cassandra/1441/workflows/55475c64-767c-432b-8c5b-3c3e5023a378/jobs/6220
repeated dtest
https://app.circleci.com/pipelines/github/instaclustr/cassandra/1443/workflows/194d0aa8-2f94-4c0f-ba65-8a3b424f060e/jobs/6224
j8 precommit
https://app.circleci.com/pipelines/github/instaclustr/cassandra/1443/workflows/97880965-7e96-436a-8a37-d43d34b85348
> 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
> Components: Feature/Virtual Tables
> Reporter: Michiel Saelen
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 4.2
>
> Attachments: signature.asc
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
