[
https://issues.apache.org/jira/browse/CASSANDRA-12944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930104#comment-15930104
]
Stefan Podkowinski commented on CASSANDRA-12944:
------------------------------------------------
bq. It feels like a lot conceptually here that overlaps with tracing.
I don't really think so. Events are only local per node and there's no concept
of sessions or state and no persistence. There's also no messaging across nodes.
bq. Do you imagine users to let this functionality run all the time when the
database is running?
Absolutely. You might be able to create monitoring tools that will constantly
run in the background for consuming events. If this really becomes a
performance strain for a node will likely depend on the number of events you're
subscribing to. E.g. if you're subscribed to all compaction events the number
of events would be bound to the compaction progress and I wouldn't expect that
the event handling would become the bottleneck in this case.
> Diagnostic Events
> -----------------
>
> Key: CASSANDRA-12944
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12944
> Project: Cassandra
> Issue Type: Improvement
> Components: Observability
> Reporter: Stefan Podkowinski
>
> I'd like to propose a new "diagnostic events" feature that would allow to
> observe internal Cassandra events in unit tests and from external tools via
> native transport. The motivation is to improve testing as well as operational
> monitoring and troubleshooting beyond logs and metrics.
> Please find more details in the linked proposal and give it some thoughts :)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
