Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support alarm discriminators #21

Open
fhunleth opened this issue Dec 11, 2024 · 0 comments
Open

Support alarm discriminators #21

fhunleth opened this issue Dec 11, 2024 · 0 comments

Comments

@fhunleth
Copy link
Collaborator

Currently Alarmist only supports atoms. Discriminating alarms of the same type, but applying to different things is possible by creating new atoms. I.e., NetworkDown.eth0. It would be far better to allow for at least 2-tuple alarms with the discriminator in the second slot. I.e., {NetworkDown, "eth0"}.

This requires updates to allow 2-tuple alarms since they're currently ignored. Alarmist should also offer ways of subscribing to events based on the Alarm ID only, the discriminator only, or both. It also requires updates to synthetic alarms.

Allowing for structured alarm discriminators like %NetworkDownAlarm{ifname: "eth0"} seems nice to think about, but might be too much for the first pass considering that it can't be completely freeform and that it invites descriptive (non-descriminator) fields.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant