Private agents
Internal services stay closed, yet they are checked just like public ones.
The task
Internal APIs, databases and brokers are not visible from the internet, and you cannot open them up just for monitoring.
How it is solved
The agent is installed in your network and pulls tasks from A3.Observe itself, so no inbound connections are needed. Variables and secrets are filled in before the task is sent: the agent receives a ready request and does not store templates. You set the list of networks the agent may reach.
What is included
- Outbound agent connections only
- Docker, systemd, Windows service and launchd on macOS
- Types: HTTP, TCP, PostgreSQL, MySQL, MongoDB, Redis, MQTT, RabbitMQ, Kafka
- Allowed networks are set on the agent side
- The token is shown once, stored as a hash, can be reissued and revoked
- Online status, version and supported types are visible in the interface
Limitations
- The agent does not run browser checks, mail or file protocol checks.
- If the agent is silent longer than the threshold, its checks are recorded as unavailable.
What depends on the plan
This feature is available in every plan and has no separate limit.
Compare plansQuestions about this feature
Do I need to open a port for the agent?
No. The agent connects to A3.Observe on its own with outbound requests.
What happens if the agent goes down?
After the set threshold, the agent’s checks get the “agent unavailable” status, and you learn about it the same way as about any other outage.
Where it helps
Other features
All featuresCheck your services today
The free plan includes checks, a status page and a team of up to three people. The setup wizard takes you from a product to the first notification.