# How it works

Follow telemetry from your application to its evidence, runtime health, and your connected agent.


Everock connects the signals your application sends with the context your agent needs to investigate. Connecting a repository adds code context; installing the SDK supplies runtime telemetry. They serve different purposes.

## Capture

Install the SDK in each application or service you want to observe. Configure its collector URL, project key, environment, release, and component where appropriate. Capture depends on the runtime, integrations, privacy settings, and sampling you enable.

## Group

Related failures are grouped by their identifying signature within a project. Repeated occurrences increase the count of an open incident. A repeated failure does not create a separate notification for every request.

## Explore

- **Home** brings together the project's telemetry, sessions, users, releases, and endpoints.
- **System** shows connected code and services, with health derived from observed traffic or explicitly configured monitors.
- **Activity & Findings** shows evidence, investigation progress, and updates from your connected agent.

## Work with your agent

Connect your agent through the CLI and MCP. The agent reads the project's available evidence, works with your repository and tools, and reports findings to Everock. Review and authorize changes in your agent application.

## Understand health

Passive monitoring uses requests your application already makes. A service with no observed traffic has insufficient data; it is not automatically healthy or down. Optional active monitors make additional requests on their configured schedule.


  A repository connection alone cannot prove that a deployed application or endpoint is healthy. Install the SDK in the runtime you want to observe, or configure an appropriate monitor.


## Choose your installation

Start with [Next.js](/docs/sdks/nextjs), [Vite](/docs/sdks/vite), [NestJS](/docs/sdks/nestjs), or [Node](/docs/sdks/node).