[jira] [Commented] (CASSANDRA-13460) Diag. Events: Add local persistency

["Stefan Miklosovic (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17382901#comment-17382901 ] 

Stefan Miklosovic commented on CASSANDRA-13460:
-----------------------------------------------

Hi [~spod],

yet another store to be implemented might be built on virtual tables. Even it would not survive restarts, I think this still has its value. Even more so if it can be queried via CQL. However, if you prefer to have it in chronicle queues solely, that is something else ...

BTW, maybe the best thing would be to make this pluggable. I was checking the implementation and right now there is just memory persistence, just hard coded. This might be configurable via cassandra.yml where a user would supply his own impl.

> Diag. Events: Add local persistency
> -----------------------------------
>
>                 Key: CASSANDRA-13460
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13460
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Legacy/Observability
>            Reporter: Stefan Podkowinski
>            Assignee: Stefan Podkowinski
>            Priority: Normal
>         Attachments: 0001-Add-persistency-for-events-to-system-keyspace.patch
>
>
> 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-  provide a dump of all events as described in the [documentation|https://github.com/spodkowinski/cassandra/blob/WIP-13460/doc/source/operating/diag_events.rst]. 
> 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
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org