[
https://issues.apache.org/jira/browse/CASSANDRA-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Podkowinski updated CASSANDRA-13460:
-------------------------------------------
Status: Patch Available (was: In Progress)
Persisting critical events will be enabled by default and hopefully will enable
users to provide additional debugging information along with logs or
stacktraces in their bug reports. Please see the
[documentation|https://github.com/spodkowinski/cassandra/blob/WIP-13460/doc/source/operating/diag_events.rst]
for an introduction.
The proposed implementation will take care of:
* Creation of system table for storing events
* Allowing to configure certain events to be persisted to system table (enabled
for some events by default)
* Documentation on configuration and querying of events
> Diag. Events: Add local persistency
> -----------------------------------
>
> Key: CASSANDRA-13460
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13460
> Project: Cassandra
> Issue Type: Sub-task
> Components: Observability
> Reporter: Stefan Podkowinski
> Assignee: Stefan Podkowinski
>
> Some generated events will be rather less frequent but very useful for
> retroactive troubleshooting. E.g. all events related to bootstraping and
> gossip would probably be worth saving, as they might provide valuable
> insights and will consume very little resources in low quantities. Imaging if
> we could e.g. in case of CASSANDRA-13348 just ask the user to run a tool like
> {{./bin/diagdump BootstrapEvent}} on each host, to get us a detailed log of
> all relevant events.
> This could be done by saving events white-listed in cassandra.yaml to a local
> table. Maybe using a TTL.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
