Create asset-based monitor setup flow #14

Closed
opened 2026-05-23 15:46:01 -06:00 by Agent · 0 comments

Implemented in bd6c508.

Summary:

  • Added an asset-first setup flow in the Assets page.
  • Users can create a new asset or select an existing asset, then attach ping, TCP, website, and SNMP monitors in any combination.
  • Asset deletion is available from the UI with confirmation that attached monitors are also removed.
  • Website, ping, and TCP monitor create APIs can attach to an existing asset without creating duplicate assets.
  • SNMP discovery selections can be saved as friendly SNMP monitors attached to an asset.
  • Monitor setup does not automatically create alert rules in the asset flow; alerting remains separate.

Verified:

  • docker compose -f docker-compose.dev.yml exec -T backend python -m pytest tests
  • docker compose -f docker-compose.dev.yml exec -T frontend npm run typecheck
  • docker compose -f docker-compose.dev.yml exec -T frontend npm run build
Implemented in bd6c508. Summary: - Added an asset-first setup flow in the Assets page. - Users can create a new asset or select an existing asset, then attach ping, TCP, website, and SNMP monitors in any combination. - Asset deletion is available from the UI with confirmation that attached monitors are also removed. - Website, ping, and TCP monitor create APIs can attach to an existing asset without creating duplicate assets. - SNMP discovery selections can be saved as friendly SNMP monitors attached to an asset. - Monitor setup does not automatically create alert rules in the asset flow; alerting remains separate. Verified: - docker compose -f docker-compose.dev.yml exec -T backend python -m pytest tests - docker compose -f docker-compose.dev.yml exec -T frontend npm run typecheck - docker compose -f docker-compose.dev.yml exec -T frontend npm run build
Agent changed title from Create monitors from SNMP discovery selections to Create asset-based monitor setup flow 2026-05-23 20:46:51 -06:00
Agent closed this issue 2026-05-23 21:07:37 -06:00
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: ksmith/OrbitWard#14