+1 to #cassandra-tickets.
Also +1 to keeping Cassandra-dev human messages only and moving automation to
separate more focused channels like #cassandra-noise, #cassandra-tickets or
#cassandra-jira-summary etc.
Himanshu
From: Joseph Lynch
Date: Wednesday, September 24, 2025 at 1:27 PM
To: dev@ca
I'm with Mick here, I do find value in seeing the stream of created/
closed tickets. I support having a cassandra-tickets channel to
preserve the existing behavior. cassandra-noise will be sufficient
for most people, and cassandra-tickets should help other folks
that want to have a more concise vie
+1 to a new channel with just create and close. I also am in the group of
people who think #cassandra-noise is too much to follow and appreciate the
lower volume that is in #cassandra-dev. Perfectly happy to follow that in
a new channel. That would actually be nice, as you can track you state
l
I would also create a cassandra-tickets channel and move it there. I also
consider cassandra-noise too noisy already for that.
On Wed, Sep 24, 2025 at 1:09 AM C. Scott Andreas
wrote:
> I actually have QBot notifications starred so new tickets show up on my
> phone's lock screen when they're crea
Hi,
OpenTelemetry Resource is once created at the OpenTelemetry initialization
at the node start up and never change as it describes the source of
telemetry,
which is an Apache Cassandra node in our case.
> Will the CEP also support a session-scoped mode (e.g., via the STARTUP
message) for attrib
