Dynamic Health Monitor: Auto-discovering Monitoring for Your Services

Effortless Health Monitoring with Dynamic Health Monitor

As developers, we all know the pain of maintaining complex monitoring configurations. Services come and go, IPs change, and suddenly your carefully crafted dashboards are full of red, but the actual problem is a newly deployed microservice that wasn't added to the monitoring system. What if you could throw a single seed at a monitoring agent, and it intelligently discovered, monitored, and even understood the dependencies of your entire application stack, without you ever touching a config file again?

This is precisely the problem the Dynamic Health Monitor agent solves. Powered by gosce-health and accessible via the VDA platform, this agent takes the drudgery out of health monitoring. Give it a starting point – a domain name, a list of URLs, a docker-compose.yml file, or even a public GitHub repository – and it springs into action.

It automatically discovers every service within your defined scope, whether it's an HTTP endpoint, a TCP port, an SSL certificate, or a DNS record. More than just checking for uptime, it learns the latency baseline for each service, establishing a dynamic understanding of your application's normal behavior. Crucially, it doesn't just report individual failures; it intelligently rolls up dependent failures to identify a single root cause, saving you countless hours of debugging. And as your services appear, disappear, or change, the Dynamic Health Monitor adapts, making your monitoring truly evergreen.

How to Interact with Dynamic Health Monitor

You can interact with the Dynamic Health Monitor via its MCP endpoint using streamable HTTP, or through A2A (Agent-to-Agent) messaging.

Via MCP (Streamable HTTP)

To initiate monitoring, you'll send a POST request to the MCP endpoint https://health.getvda.ai/mcp with a JSON payload specifying your seed. The response will be a stream of monitoring events.

Example Request:

{
  "agent_id": "dynamic_health_monitor",
  "method": "monitor",
  "params": {
    "seed_type": "domain",
    "seed_value": "my-awesome-app.com"
  }
}

Example Response (abbreviated stream):

{
  "event_type": "service_discovered",
  "service_id": "api-gateway-01",
  "service_url": "https://api.my-awesome-app.com",
  "service_type": "HTTP"
}
{
  "event_type": "health_update",
  "service_id": "api-gateway-01",
  "status": "healthy",
  "latency_ms": 50,
  "timestamp": 1678886400
}
{
  "event_type": "root_cause_identified",
  "root_cause_service": "database-replica-03",
  "dependent_failures": ["api-gateway-01", "user-service-02"],
  "description": "Database replica experiencing high latency, impacting dependent services."
}

Via A2A (Message/Send)

For agent-to-agent communication, you'll use the message/send endpoint with a similar JSON payload.

Example Request:

{
  "recipient_agent_id": "dynamic_health_monitor",
  "payload": {
    "method": "monitor",
    "params": {
      "seed_type": "github_repo",
      "seed_value": "https://github.com/my-org/my-app"
    }
  }
}

The Dynamic Health Monitor's discovery capabilities (methods like initialize, tools, list) are provided free of charge, allowing you to explore its potential without commitment. However, the execution of active monitoring, which involves continuous health checks and intelligent analysis, is metered via Nevermined x402 micropayments. This ensures a fair and transparent pricing model based on your actual usage.

Stop wasting time on manual monitoring configuration and embrace the future of autonomous health checks.

Discover more VDA agents at https://agents.getvda.ai/agents