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

Post event when device disappears from a netbox #2392

Open
2 tasks
Tracked by #1997
lunkwill42 opened this issue Apr 29, 2022 · 4 comments
Open
2 tasks
Tracked by #1997

Post event when device disappears from a netbox #2392

lunkwill42 opened this issue Apr 29, 2022 · 4 comments
Assignees
Labels
discussion Requires developer feedback/discussion before implementation nav-ref Fronted by the NAV user reference committee

Comments

@lunkwill42
Copy link
Member

lunkwill42 commented Apr 29, 2022

@lunkwill42
Copy link
Member Author

In reality, this is two events:

  1. Device was removed from a netbox
  2. Device appeared on another netbox

@lunkwill42 lunkwill42 changed the title Post event when device moves from one netbox to another Post event when device disappears from a netbox Jun 10, 2022
@lunkwill42
Copy link
Member Author

In reality, this is two events:

1. Device was removed from a netbox

2. Device appeared on another netbox

Changed the wording of this issue. We are already working on number 2, so this issue is really about number 1: Notify when devices are removed.

@stveit
Copy link
Contributor

stveit commented Dec 1, 2022

some alerts for reporting that a device has disappeared already exist, like chassisDown and moduleDown alerts. These are meant for devices suddenly going missing, but I dont know how to differentiate between a device randomly dying and a device being purposefully removed from the netbox.

PR #2414 adds alerts when a Chassis, Module or PowersupplyOrFan pops up on a netbox, To compliment that here only events for PowersupplyOrFan devices disappearing are missing. But PowersupplyOrFan are a little different, as they have no UP and DOWN states like chassis and modules have, they simply get deleted if they are found to be missing. So new events called psuDeleted and fanDeleted or something might cover this.

My questions:

  • do the already existing chassisDown and moduleDown cover chassis and modules already? Or should some new alerts be created that behave differently?
  • Are there any events other than chassis, modules and Psu/fans dissapearing that should be covered by this issue?

@lunkwill42 lunkwill42 added the discussion Requires developer feedback/discussion before implementation label Mar 20, 2023
@johannaengland johannaengland added the nav-ref Fronted by the NAV user reference committee label Sep 16, 2024
@stveit
Copy link
Contributor

stveit commented Sep 18, 2024

for chassis and modules: add deviceDeletedChassis and deviceDeletedModule when chassis and module are manually and intentionally deleted via status2 (delete_module_or_chassis) and devicehistory (do_delete_module)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Requires developer feedback/discussion before implementation nav-ref Fronted by the NAV user reference committee
Projects
Status: 🏗 In progress
Development

No branches or pull requests

3 participants