Data you own
Most monitoring tools copy your telemetry onto their own servers, then let you read it back. icLens works the other way round: every part of the pipeline is a canister you control, running on the Internet Computer next to your app.
What runs where
Section titled “What runs where”| Part | What it is | Who controls it |
|---|---|---|
| Your Agent | Watches your canisters and keeps Metrics, Logs and Traces | You (and the Agent itself) |
| A separate store | Optional: a Metrics, Logs or Traces store in its own canister, for a large fleet | Your Agent, and you for recovery |
| A frontend collector | Receives measurements from your website’s visitors | Your Agent, and you for recovery |
Each one is installed from a published icLens release, checked against its module hash before it runs. You can upgrade, recover or remove any of them.
What that gives you
Section titled “What that gives you”- No vendor in the middle. Nobody else stores or meters your telemetry.
- You choose retention. Keep data as long as your storage allows.
- You pay in cycles. Storage and compute are paid from your Agent’s cycles, like any canister you run. icLens deducts nothing from your top-ups.
- Your team, your rules. Access is set by your Agent’s roles, not by an outside account.
Where data does leave
Section titled “Where data does leave”Data leaves the Internet Computer only when you send it:
- Alerts and daily digests sent to Slack or a webhook you configure.
- Questions you ask the AI assistant, which go to the IC’s LLM service with the evidence for that question.
- Tools you connect, such as Grafana, read with a credential you issue and can revoke.
Owning the canister is not encryption: like any canister, the subnet’s nodes can see its memory. Don’t send secrets in logs or metric labels.