Create events from SystemLogger

[burmanm]

What is missing?
If we have issues in the running pod which are visible from the Cassandra logs, we could create events directly from the SystemLogger which we deploy as a sidecar to every Cassandra pod. This ensures that the log processing will scale no matter how many nodes the cluster has (assuming low amount of events are generated).

We could still output the logs to the stdin also, with possibility of more features for filtering. However, I don't think we should necessary implement these features ourselves (the parsing language, tailing etc), instead we could use a logshipper such as Vector (but not necessarily Vector) and then modify the rules to be available in a ConfigMap if user wishes to further use its capabilities in their log shipping requirements.

We probably need to create the Kubernetes events sink ourselves as not many products have that. Or just to create the events, we can add a webhook to cass-operator and call it with the service name - however this then requires that cass-operator does not become the bottleneck in large clusters and that it is always available (or we need to queue on the sending side + throttling etc).

k8ssandra/management-api-for-apache-cassandra#193

Why do we need it?

Environment

• Cass Operator version:

  Insert image tag or Git SHA here

  **Anything else we need to know?**:

┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: CASS-42

[jsanda]

Isn't this a duplicate of k8ssandra/management-api-for-apache-cassandra#193?

[burmanm]

This was intended as alternative approach. Both would achieve the same.

…

On Tue, Jun 7, 2022, 05:27 John Sanda ***@***.***> wrote: Isn't this a duplicate of k8ssandra/management-api-for-apache-cassandra#193 <k8ssandra/management-api-for-apache-cassandra#193> ? — Reply to this email directly, view it on GitHub <#338 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEJLDTAJFPXDQEZF5QY4QLVN2XSRANCNFSM5XRPB7RQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>