You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Stefan Miklosovic (Jira)" <ji...@apache.org> on 2021/09/10 13:20:00 UTC
[jira] [Commented] (CASSANDRA-13460) Diag. Events: Add local
persistency
[ https://issues.apache.org/jira/browse/CASSANDRA-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413180#comment-17413180 ]
Stefan Miklosovic commented on CASSANDRA-13460:
-----------------------------------------------
Hi [~spod], do you plan to work on this? I have WIP branch here (1) which is fetching events from stores and it displays them in vtable. We plan to also introduce a helper (mutable) vtable once CASSANDRA-16806 is in via which one might enable / disable events conveniently from CQL shell.
If we want to survive reboot, I plan to cover that by implementing Chronicle Queues impl, same way as it was done for FQL / Audit but that I want to cover in a separate ticket.
(1) https://github.com/apache/cassandra/pull/1194/files
> 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