[
https://issues.apache.org/jira/browse/CASSANDRA-17197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17502922#comment-17502922
]
Andres de la Peña commented on CASSANDRA-17197:
-----------------------------------------------
Here is the patch adding diagnostic events for guardrails:
||PR||CI||
|[trunk|https://github.com/apache/cassandra/pull/1485]|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/1340/workflows/58cc1a02-7a5a-4d60-869f-c698b56d66df]
[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/1340/workflows/2ea9c9a1-288f-4c64-9839-611e640da42b]|
It creates a new type of diagnostic event called
[{{GuardrailEvent}}|https://github.com/adelapena/cassandra/blob/17197-trunk/src/java/org/apache/cassandra/db/guardrails/GuardrailEvent.java].
There are two types on guardrail event, which are {{WARNED}} and
{{{}FAILED{}}}, matching the soft and hard activation of the guardrail. These
events carry two properties, which are the name of the specific guardrail and
the specific error message.
As for testing, there is a consumer/listener for the new type of diagnostic
events attached to every {{{}GuardrailTester{}}}, so every time that we check
the activation of a guardrail we also check that the proper events have also
been emitted.
> Diagnostic events for guardrails
> --------------------------------
>
> Key: CASSANDRA-17197
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17197
> Project: Cassandra
> Issue Type: New Feature
> Components: Feature/Guardrails
> Reporter: Andres de la Peña
> Assignee: Andres de la Peña
> Priority: Normal
>
> Add diagnostic events for guardrails, so we can monitor when each type of
> guardrail is triggered.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
