Subscribe to notifications
The operator creates a subscription naming the receiver endpointEndpointA particular address on a service that accepts a defined kind of request. and the findingFindingA difference in the records that needs a decision. It includes its sources and can describe a slow handoff, disputed fact or missing owner. kinds it should hear about. Receivers are bounded: never a cloud metadata or link-local address, loopbackLoopbackA network address that refers to the same host, such as 127.0.0.1. Other hosts cannot reach a service through that address. only when the deployment allows it, and only hosts on the allow-listAllow-listA list of permitted actions, resources or destinations. It excludes everything else only when its issuer says the list is complete. when one is set.
The Docker stack does not start a notification watcher. Creating a subscription does not start delivery. Run a poll in the configured reasoning containerContainerA running program with its own packaged software and isolated environment, managed by Docker on the host.:
./lens connectors notify poll --org <org> \
--viewer <operator-login> --base-url <browser-base-url>Replace every placeholder. Use the installer’s operator login and browser address without /login, including its chosen port. Use the same --viewer for subscription and delivery commands. For continuing delivery, the operator must run or schedule notify watch; a container restart does not schedule it. See the operator shell and notification operations.
Each delivery is recorded with the reason sent and its outcome. Failures retry with backoffBackoffA delay before retrying a failed operation. The delay usually grows after repeated failures to avoid making an outage worse.. Use the deliveries listing to check what was issued and how long after the finding moved.