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

Distinct enabled state monitoring #15

Merged
merged 3 commits into from
Aug 10, 2023

Conversation

kpetremann
Copy link
Contributor

@kpetremann kpetremann commented Aug 2, 2023

Implements: #7

Before this commit, both the state and the up/down intent were merged.

It was preventing us from declaring a BGP session in maintenance while
shutting the BGP only on one side.

With this commit, state and enabled are completely separate.

We do not reuse "status" from NetBox DCIM:
- to avoid conflict if we want to redefined the state at the device
  level
- "state" is more appropriate to define if a device is in
  production/validation etc... Status is really accurate.

"enabled" is the same as in OpenConfig and minimize possible
misinterpretation of what it does.
Monitoring state defined the criticity of monitoring alerts for the
asset.

Possible usage:
- critical: on-call alerts
- warning: working-hours alerts only
- disabled: no alerts (lab, tests, etc...)

The recommended implementation would be to only consider the monitoring
state if a device is in production, because:
- there is no reason to raise an alert for a device not in production
- if we have to change the monitoring status during a maintenance/issue,
  it would be difficult to know what is the expected status once back to production
@kpetremann kpetremann requested review from a team August 8, 2023 13:35
@kpetremann kpetremann merged commit 617005e into criteo:main Aug 10, 2023
2 checks passed
@kpetremann kpetremann deleted the distinct-enabled-state-monitoring branch August 10, 2023 08:59
kpetremann added a commit to kpetremann/data-aggregation-api that referenced this pull request Aug 10, 2023
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

Successfully merging this pull request may close these issues.

2 participants