> > If one subscribes via JMX, this subscription is not propagated to the > underlying CQL table. So she might subscribe to 5 events but there > would be none in vtable.
There isn't any need for any underlying CQL table here. The enabled state, and subscriptions, is in DatabaseDescriptor and DiagnosticEventService. Both interfaces: JMX and vtable; would update these values. And it is intentional that any changes made at runtime are reset when a node restarts. If the events are implemented to be persisted in a chronicle queue, then they will be available after a restart (readable via either jmx or vtable). Let's continue this discussion on CASSANDRA-13460.
