'%20filter='url(%23b)'%20transform='translate(0%20-286)'/%3e%3cpath%20d='M1636.5%20147c-123.436%200-223.5%20102.975-223.5%20230s100.064%20230%20223.5%20230S1860%20504.025%201860%20377c-.143-126.964-100.124-229.853-223.5-230Zm107.16%20308.341c-1.892%202.323-4.973%203.231-7.78%202.295l-98.896-32.908-98.896%2032.908c-2.807.933-5.884.022-7.774-2.3-1.89-2.32-2.212-5.587-.815-8.25l101.128-192.49c1.376-2.238%203.776-3.596%206.357-3.596%202.58%200%204.981%201.358%206.357%203.596l101.128%20192.49c1.401%202.663%201.08%205.932-.81%208.255Z'%20fill='url(%23c)'%20filter='url(%23d)'%20transform='translate(0%20-286)'/%3e%3c/g%3e%3c/svg%3e)
Monitoring sources and notification channels
Monitoring sources and notification channels are the org-level glue between probe execution and human or system responses.
Monitoring sources
Sources represent vantage points from which checks can run - typically agent-backed hosts exposing capabilities such as HTTP, TCP, UDP, SSL.
Organization APIs list hosts whose agents are eligible as sources, including capability tags, location hints, and health heartbeats. UI and automation use this list when attaching a monitoring object to a specific probe origin.
Background alignment keeps source health consistent with agent and host state changes.
Notification channels
Channels route firing alerts to destinations. Supported delivery modes include:
- Email - role-targeted mail.
- In-product - notifications for users holding selected roles.
- Webhook - HTTPS endpoints with URL validation before save.
Channels support filters (severity, internal-only routing) and RBAC separate from monitoring object permissions.
Alerts and channels themselves are configuration documents; the scheduler evaluates monitoring objects, while channels are consumers of alert lifecycle events.