Monitor a frontend
Open Telemetry › Frontends to investigate what your visitors experience. Start with what changed, size its impact, open a real example, then follow the evidence to its cause. The collector is a canister managed by the selected Agent; it keeps this site’s measurements, errors, events and timelines itself.
An Admin sets up collection. People in the Agent workspace read the collector with their own identity. Access follows People automatically, up to the collector’s 32-person limit. Independent controller authority is separate from membership. Settings › Collector shows access still to remove when a removed or inactive person retains native read access. Pending access changes retry automatically; an Admin can check their current state there.
-
Choose Monitor a frontend. Enter the site’s name and hostnames, and list the canisters and other services whose calls it measures. Approve the page paths and operations the site records; a canister’s address alone does not identify the method its application code calls.
-
Choose a new collector, an existing managed collector, or adopt one that both you and the Agent control. Adoption does not change controllers. Review the storage limits, retention and initial funding before creating a canister.
-
Choose What to record. Approve detailed errors, events and timelines separately from aggregate measurements. Detailed evidence needs an immutable build name and bounded approved definitions.
-
Review the exact operation and Run as before confirming. Setup stages collection off while applying the reviewed configuration. An uncertain outcome needs reconciliation; starting the workflow again can create a second collector.
-
Add the generated snippet to the site. Connect its explicit consent input to your consent manager; do not treat loading the snippet as consent. Reopen the site and check its first received visit. Local snippets include the selected loopback gateway’s trusted public root key. Mainnet snippets use the Internet Computer root of trust.
Follow an investigation
Section titled “Follow an investigation”Overview brings together experience, page views, error rate and calls that didn’t get through. Needs attention links to the affected issue, page, call or release comparison.
Pages rates loading, responsiveness and layout stability at the 75th percentile. Open a page for browser and device comparisons, slow files, related errors and calls, and real examples. Missing timing remains missing.
Issues ranks retained error groups by impact. Open an issue for its type, message, seen count, affected sessions and visitors, original source, and What happened before. Seen counts and affected sessions describe different populations. A release filter or retention boundary can limit what is known.
Calls separates canisters from other services. A canister reject arrives as HTTP 200: “didn’t get through” counts HTTP errors, network errors and cancelled requests, rather than application-level rejects.
Open an Example to see its Timeline. When the site carries the context into an instrumented canister call, Continue in canister includes that canister’s recorded steps. Otherwise icLens explains the missing continuation and links to the canister. It never guesses missing steps.
Events appears when the site records custom events. Visitors remains off until counting is enabled. Its exact report covers retained whole UTC days; a visitor means a browser, not an identified person. Several days’ unique visitors are counted once, never added from daily totals.
Good to know
Section titled “Good to know”- Every figure identifies exact retained accounting or estimated measurements. Sampling, missing coverage and unavailable intersections stay explicit.
- Upload original-source artifacts from Settings › Site using the exact release manifest, build binding, generated script URL and map. The protected upload requires an active Agent Admin to register the release and your own authority on the protected artifact host under Run as You. Uploading a map does not approve extra private error content for collection. Supply its access code before the upload review; the code stays in session memory.
- Create rule opens a Monitor rule draft for review and saving. Create a dashboard starts from the collector’s editable templates with this exact site as their source. The Experience template remains available when approved recording codes have no display names. Measurement templates require those names; the review explains the missing prerequisite without inventing labels. New issue in latest release needs five minutes of accepted collector history. Missing, stale or incomplete evidence remains unavailable rather than being treated as no new issue. The Visitors panel reads the whole-day report directly. Storage and running cost show measured facts; configured capacity is not a traffic guarantee. Timeline allocation reports the native arena’s allocated memory and available admission bytes. Logical occupied storage remains unavailable unless reported.