Body:
Danbyte currently has no way to track planned maintenance or unplanned outage events from providers/carriers against infrastructure objects (circuits, devices, sites, etc.), and no way to automatically create these events from provider notification emails.
Core data model:
Maintenance and Outage as distinct event types, tied to a provider
Generic Impact model linking an event to any configured object type (circuit, device, site, prefix, IP, etc.) with an impact level (no-impact / reduced-redundancy / degraded / outage)
Status workflows per event type (maintenance: tentative → confirmed → in-progress → completed/cancelled/rescheduled; outage: reported → investigating → identified → monitoring → resolved) with ETR tracking on outages
Calendar view + iCal feed for external calendar subscription
Email ingestion:
Ability to point the system at a mailbox (IMAP or forwarding address) that receives provider maintenance/outage notifications
Parse incoming emails and automatically create/update Maintenance or Outage records from them, rather than requiring manual entry
Store the raw email alongside the parsed event for reference/audit
Since providers format notifications differently, this likely needs per-provider (or pluggable) parsers rather than one generic parser — netbox-notices keeps parsing external to the plugin (REST API + separate parser components, e.g. their AWS SES/SNS Lambda examples); worth considering whether Danbyte does this in-app or via a similar external-parser + API pattern
Examples:
https://networktocode.com/nautobot/nautobot-apps/circuit-maintenance/
https://github.com/jsenecal/netbox-notices
Big thanks for all the work!!
Body:
Danbyte currently has no way to track planned maintenance or unplanned outage events from providers/carriers against infrastructure objects (circuits, devices, sites, etc.), and no way to automatically create these events from provider notification emails.
Core data model:
Maintenance and Outage as distinct event types, tied to a provider
Generic Impact model linking an event to any configured object type (circuit, device, site, prefix, IP, etc.) with an impact level (no-impact / reduced-redundancy / degraded / outage)
Status workflows per event type (maintenance: tentative → confirmed → in-progress → completed/cancelled/rescheduled; outage: reported → investigating → identified → monitoring → resolved) with ETR tracking on outages
Calendar view + iCal feed for external calendar subscription
Email ingestion:
Ability to point the system at a mailbox (IMAP or forwarding address) that receives provider maintenance/outage notifications
Parse incoming emails and automatically create/update Maintenance or Outage records from them, rather than requiring manual entry
Store the raw email alongside the parsed event for reference/audit
Since providers format notifications differently, this likely needs per-provider (or pluggable) parsers rather than one generic parser — netbox-notices keeps parsing external to the plugin (REST API + separate parser components, e.g. their AWS SES/SNS Lambda examples); worth considering whether Danbyte does this in-app or via a similar external-parser + API pattern
Examples:
https://networktocode.com/nautobot/nautobot-apps/circuit-maintenance/
https://github.com/jsenecal/netbox-notices
Big thanks for all the work!!