# Ottertrail > Ottertrail is web analytics, product analytics, error tracking, session replay, and monitoring for small software teams, in one tool. Each customer runs an instance of their own. These are Ottertrail's user documentation pages. A site sends events to its own Ottertrail instance, at the instance's own address. Keep each project's secret key (`sk_…`) on servers only: pages and browser code use the public key (`pk_…`). - [Complete documentation](https://docs.ottertrail.app/llms-full.txt): every page below as Markdown, in this order. ## Introduction - [What is Ottertrail](https://docs.ottertrail.app/introduction/what-is-ottertrail/): What Ottertrail does, which data it collects, and how it treats visitors' data. - [How an instance is organised](https://docs.ottertrail.app/introduction/instances-and-projects/): Instances, projects, keys, environments, and the people who use the dashboard. - [The dashboard](https://docs.ottertrail.app/introduction/the-dashboard/): The workspace and a project's menu, and how reports, lists, and settings work on every screen of the dashboard. - [The overview](https://docs.ottertrail.app/introduction/overview/): The project's first page, with ten widgets on errors, uptime, servers, speed, goals, users, and traffic, and how to arrange them. - [Project settings](https://docs.ottertrail.app/introduction/project-settings/): The seven tabs of a project's Settings page, what each one holds, and the Danger zone. ## Get started - [Get started](https://docs.ottertrail.app/get-started/): The steps from an empty server to data in the dashboard, and a prompt that gives the same steps to a coding agent. - [Install Ottertrail](https://docs.ottertrail.app/get-started/install/): Install a self-hosted Ottertrail instance on a Linux server with Docker Compose, from a GitHub release. - [The first start](https://docs.ottertrail.app/get-started/first-start/): Start the instance, create the owner account with the setup link, and check that the location data arrived. - [Create a project and add the tracker](https://docs.ottertrail.app/get-started/add-the-tracker/): Create a project in the dashboard, allow your site's hostnames, and add the tracker snippet. ## Web analytics - [Web analytics reports](https://docs.ottertrail.app/web-analytics/reports/): The numbers on the Web analytics page: visitors, visits, pageviews, bounce rate, time engaged, sources, breakdowns, and filters. - [Environments and releases](https://docs.ottertrail.app/web-analytics/environments-and-releases/): Keep staging traffic out of the live numbers, and see which release each visit used. - [Spam and bots](https://docs.ottertrail.app/web-analytics/spam-and-bots/): Which visits Ottertrail ignores as bots and spam, the project's Spam and bots settings, and deleting spam that got in. - [Web Vitals](https://docs.ottertrail.app/web-analytics/web-vitals/): How fast each page load felt, on the Speed page: LCP, INP, CLS, FCP, and TTFB. - [Heatmaps](https://docs.ottertrail.app/web-analytics/heatmaps/): Where visitors click on a page and how far they scroll, the Heatmaps report, and the heatmap drawn over your live site. ## Product analytics - [Custom events](https://docs.ottertrail.app/product-analytics/custom-events/): Send your own events with properties, and break them down in reports. - [Server-side events](https://docs.ottertrail.app/product-analytics/server-side-events/): Send events from your own server, such as payments, with the secret key. - [Funnels](https://docs.ottertrail.app/product-analytics/funnels/): See how many users go through an ordered series of steps. - [Retention](https://docs.ottertrail.app/product-analytics/retention/): See how many signed-in users come back after their first visit. - [Goals](https://docs.ottertrail.app/product-analytics/goals/): Count the visitors who reach a page or send an event, as a share of all visitors. ## Users - [Name signed-in users](https://docs.ottertrail.app/users/naming-users/): Tell Ottertrail which of your users is signed in, on page loads and in single-page apps. - [Sign user IDs](https://docs.ottertrail.app/users/signed-user-ids/): Make your server sign each user ID, so that nobody can send events that claim to be another user. - [The Users page](https://docs.ottertrail.app/users/the-users-page/): The list of the users your site names, and each user's own page with their events, errors, and replays. ## Errors - [Report errors from the browser](https://docs.ottertrail.app/errors/browser-errors/): Which browser errors the tracker reports automatically, and how to report the errors your app catches with captureError. - [Upload source maps](https://docs.ottertrail.app/errors/source-maps/): Upload your build's source maps with the secret key, so that error stacks show your own files and lines. - [How errors are grouped](https://docs.ottertrail.app/errors/grouping/): How Ottertrail puts occurrences of one bug in one group. - [Resolving errors](https://docs.ottertrail.app/errors/resolving/): The Errors page and an error's own page: mark a group resolved, reopen it, and see when it comes back. - [Server errors](https://docs.ottertrail.app/errors/server-errors/): Exceptions from your servers, sent over OpenTelemetry, in the same error list. ## Session replay - [Replays of errors](https://docs.ottertrail.app/session-replay/error-replays/): Ottertrail records the moments before an error, and never whole sessions. Find replays and play them back. - [Masking and privacy](https://docs.ottertrail.app/session-replay/masking-and-privacy/): What the recorder hides in the visitor's browser before anything is sent. - [Turn on session replay](https://docs.ottertrail.app/session-replay/turning-it-on/): The project setting and the script attribute that both turn replays on, and how to delete a project's replays. ## Monitoring - [Send telemetry](https://docs.ottertrail.app/monitoring/sending-telemetry/): Send traces, logs, and metrics from your servers to Ottertrail over OpenTelemetry, with setup for Go, Node.js, and Python. - [Traces](https://docs.ottertrail.app/monitoring/traces/): Find a request's trace, and follow it through its spans and logs. - [Logs](https://docs.ottertrail.app/monitoring/logs/): Search your servers' log records by words, severity, service, and trace. - [Metrics](https://docs.ottertrail.app/monitoring/metrics/): Chart your servers' gauges, counters, and histograms. - [Services](https://docs.ottertrail.app/monitoring/services/): Requests, failures, and durations for each service and route. - [Databases](https://docs.ottertrail.app/monitoring/databases/): The database calls inside your traces, grouped by query shape. - [Hosts](https://docs.ottertrail.app/monitoring/hosts/): Send your servers' CPU, memory, filesystem, network, disk, and load metrics with the OpenTelemetry Collector. ## Uptime and alerts - [Uptime checks](https://docs.ottertrail.app/uptime-and-alerts/checks/): Check a URL on a schedule, and see its uptime, response time, and incidents. - [Alert rules](https://docs.ottertrail.app/uptime-and-alerts/alert-rules/): Get told when a check goes down, an error appears, or a metric crosses a value. - [Notification channels](https://docs.ottertrail.app/uptime-and-alerts/channels/): Email and webhook channels, where alerts go. - [Verify webhook signatures](https://docs.ottertrail.app/uptime-and-alerts/webhook-signatures/): Check that a webhook request came from your Ottertrail instance and is not a replay, with examples in Node.js, Python, and Go. ## Team - [Members and roles](https://docs.ottertrail.app/team/members-and-roles/): The owner, admins, and members, the Members page, and a member's access by area and project. - [Invitations](https://docs.ottertrail.app/team/invitations/): Invite a teammate with a link that you copy and send, and renew or revoke it. - [Password reset links](https://docs.ottertrail.app/team/reset-links/): Make a one-time link that sets a new password, from the Members page or from the server. - [Hand over ownership](https://docs.ottertrail.app/team/ownership/): Make another user the owner of the instance. ## Self-hosting - [Configuration reference](https://docs.ottertrail.app/self-hosting/configuration/): Every setting of a self-hosted instance in its .env file, the values the Compose file sets, and the settings for running the image without it. - [Update Ottertrail](https://docs.ottertrail.app/self-hosting/updating/): Move a self-hosted instance to a new release, pin a release, and go back to an earlier one. - [Backups and restore](https://docs.ottertrail.app/self-hosting/backups/): Back up a self-hosted instance with backup.sh, and restore it with restore.sh, with or without the object store. - [Object storage](https://docs.ottertrail.app/self-hosting/object-storage/): Choose where source maps and session replays are stored, with Garage on the same server, Cloudflare R2, Amazon S3, or no object store. - [Storage and warnings](https://docs.ottertrail.app/self-hosting/storage/): The Storage tab of the instance settings: what fills the server's disk, the storage warnings and where they go, and what the instance does when the disk is full. - [Location data](https://docs.ottertrail.app/self-hosting/location-data/): How the instance keeps its location database and data-center ranges current, the Location data tab, and updating the files by hand. - [Server commands](https://docs.ottertrail.app/self-hosting/server-commands/): The commands you run on the server, setup.mjs, reset-password.mjs, and update-geo.mjs, and when you need each. - [Behind a proxy or tunnel](https://docs.ottertrail.app/self-hosting/reverse-proxy/): How the instance finds each visitor's address behind its own Caddy, why another proxy in front breaks that, and how TRUST_PROXY works. - [Security notes](https://docs.ottertrail.app/self-hosting/security/): What to protect on a self-hosted instance, and what Ottertrail does to protect your data and your visitors. ## Reference - [Tracker reference](https://docs.ottertrail.app/reference/tracker/): The tracker's script tag, every data attribute, the window.ottertrail JavaScript API, and what the tracker sends. - [HTTP API reference](https://docs.ottertrail.app/reference/http-api/): The endpoints that send data to an instance: browser events, server-side events, source maps, and OpenTelemetry, with their requests and answers. - [Webhook payloads](https://docs.ottertrail.app/reference/webhook-payloads/): The JSON body of each webhook request, version 1, and every event type with an example. - [Limits](https://docs.ottertrail.app/reference/limits/): The sizes, rates, and budgets that an instance applies to events, heatmaps, source maps, telemetry, and webhooks.