Applications

Monitor the services running next to your workloads.

WatchLog finds databases, caches, queues and proxies in what its agents already see: in a Kubernetes cluster, in Docker, or installed on the host of a Linux server. Connect one with the command it writes for you, or none, and get a full page, default alerts and plain-language reasons.

Coming next

How integrations work

  1. 01

    Found automatically

    The agents already see each container's image and ports, and each service installed on a server's host. WatchLog lists what it recognises on the Applications page; press Monitor on the ones you want.

  2. 02

    Connected with the command it writes

    When a read-only user is needed, WatchLog writes the exact command with your names and a generated password. Or keep the password yourself, in a Kubernetes Secret or a file on the Docker host.

  3. 03

    A page, alerts and reasons

    Every service gets a full page, default alerts and sentences that explain problems, with the workloads and containers that use it.

Read-only by construction: a fixed list of statements and commands for each kind of service, and monitoring roles only. On Linux servers the install runs the integrations collector next to the agent; with docker run agents, the service page gives its command. On Kubernetes the chart already runs it. What the collector can do.