Feature

Service Monitoring & Health Checks

Monitor microservices with HTTP health checks, configurable intervals, assertion rules, and email alerts — integrated into your project management workflow.

Monitoring Built Into Your Project Workflow

Most monitoring tools exist in a silo — separate dashboards, separate accounts, separate context. Companyverse integrates service monitoring directly into your project management environment. When a service goes down, the alert connects to the team, the project, and the code that owns it.

Service Registry

Catalog all your microservices in one place with Companyverse's service registry:

Service profiles — Name, description, repository, tech stack, owning team
Dependency mapping — Interactive graph showing which services depend on each other
API contracts — Link OpenAPI specs, gRPC definitions, or event schemas to each service
Ownership tracking — Know instantly who owns each service when incidents happen

The dependency graph updates automatically as you add services and define relationships. Visual mapping makes it easy to assess blast radius during incidents.

HTTP Health Checks

Configure health checks for any HTTP endpoint:

Configurable intervals — Check every 30 seconds, 1 minute, 5 minutes, or custom
Assertion rules — Validate status codes, response body content, response time thresholds, and header values
Multi-region checks — Monitor from multiple locations to distinguish local vs. global outages
SSL certificate monitoring — Alert before certificates expire

Example Health Check Configuration

Service: API Gateway
  Endpoint: https://api.example.com/health
  Interval: 60 seconds
  Assertions:
    - Status code: 200
    - Response time: < 500ms
    - Body contains: "status": "healthy"
  Alert after: 2 consecutive failures
  Notify: #oncall-channel, ops@example.com

Alerting

When health checks fail, Companyverse triggers alerts through:

Email notifications — Configurable recipients per service
Slack integration — Post alerts to specific channels
In-app notifications — Real-time updates in your project dashboard

Alerts include context: which service failed, which assertion was violated, the full response received, and links to the service's project board for quick triage.

Uptime Dashboard

Track service reliability over time with uptime dashboards:

30-day, 90-day, and 12-month uptime percentages
Response time percentiles (p50, p95, p99)
Incident timeline showing when outages occurred and how long they lasted
SLA tracking (99.9%, 99.95%, 99.99%) with remaining error budget

Incident → Task Pipeline

When an incident occurs, Companyverse can automatically create a task in the relevant project with:

Service name and failure details pre-filled
Assigned to the service's owning team
Priority set based on severity rules
Linked to the service registry entry

This closes the loop between monitoring and project management — no manual ticket creation during incidents.

Knowledge Graph Integration

Services in the registry are nodes in Companyverse's knowledge graph. This means you can visualize relationships between services, the teams that own them, the projects they belong to, and the documentation that describes them — all in one interactive graph.

Compare: Companyverse vs. Dedicated Monitoring Tools

Capability	Companyverse	PagerDuty	UptimeRobot
Health checks	✅	Via integration	✅
Service registry	✅ With dependency graph	✅ Service directory	❌
Project management	✅ Integrated	❌ Separate tool	❌ Separate tool
Auto-create tasks	✅ Native	⚠️ Via Jira integration	❌
Team ownership	✅ From project	✅ Escalation policies	❌
Starting price	Free (3 projects)	$21/user/mo	Free (50 monitors)

Back to homepage to see all features, or try it free.

Try It Free →