What your team can do in Logister.

Positioning

Use Logister when production problems need a visible workflow.

The product is organized around the work a team does after an app starts sending signals: scan the dashboard, open the project, choose an issue, assign or close it, and use the detail tabs to understand what happened. The same project screen also holds setup, notifications, team access, and cleanup controls so the day-to-day workflow stays close to the monitored app.

Connect services

Start each monitored app as a project.

A project is the workspace for one app or service. It keeps API keys, events, settings, notifications, team access, and retention choices scoped to that app.

Creating a project is a short guided flow: choose the platform that will send telemetry, name the project, and set its data retention. Logister then opens the project's setup path at its first step, where you create the API key (a mobile token for Android and iOS) and send the first event. If you would rather fill in one page, choose Use the quick form on the first step.

Guided setup

See what is left to set up, and finish it one step at a time.

Settings > Setup lists everything a project can use, grouped by what it unlocks. Steps complete themselves when Logister sees the evidence, such as a first event, a recorded deployment, or a teammate with access; nothing is ticked off by hand. Each step names who does it: you or a project manager in Logister, your code or CI, or the Logister admin when it depends on an instance setting.

Choose Open path to work through a group one step per screen. Steps done in Logister show the same form Settings uses. Steps done in your code show the integration guide next to a live check that notices the evidence on its own; Check again checks immediately. Save and exit returns to Setup, and progress is never lost because it is read from evidence.

• The project header shows the setup state on every page, for example Live with the number of recommended steps left. Select it to open Setup.
• The dashboard lists projects that are still waiting for their first data under Finish setting up.
• Recommended and optional steps you do not need can be marked Not needed, and undone later. Required steps cannot be skipped.
• A step that depends on an instance setting, such as outbound email or the GitHub App, shows as blocked and names the Logister admin. Admins get a direct link to the setting.

Project navigation

Every project has the same sections.

The tabs under the project name are the same for every project type, so a Ruby service, an Android app, and a Cloudflare Pages site are all read the same way. What changes is the evidence inside each section. A section that has more than one view shows them just below the tabs.

• Explore keeps your time window, environment, and release when you move between Events, Charts, and Connected.
• The ? button next to the project name lists walkthroughs for the current section, page tips, and the integration docs.
• Picking another project from the Projects menu keeps the section you are in, so you can compare Issues across apps without clicking back to each overview.

Dashboard overview

Use the dashboard for cross-app signal before opening a project.

The dashboard has two jobs. Overview is for today's cross-app work: the big chart shows overall activity, My assignments shows work owned by you, and Needs attention highlights open issues that should not be buried in project cards. Projects is for scanning app health one project at a time. Projects that have not received data yet appear at the top under Finish setting up, with a link to continue their setup.

• Use Explorer when you want to know whether the whole account is getting noisier, quieter, or changing shape by event type.
• Use My assignments when you already own errors and need to get back to them quickly.
• Use Needs attention when you want a short list of open problems sorted by recent activity.
• Switch to Projects when you want to compare apps rather than investigate one chart.

Dashboard rhythm

Start broad, then open the smallest useful view.

• AccountUse Explorer to spot volume and shape changes across every app.
• OwnershipUse My assignments when the next action already belongs to you.
• QueueUse Needs attention when the team has not claimed the newest open work.

Charts

Use Explore › Charts to build a live view from Issues, Events, and Performance signals.

Explore › Charts, also called the Insights workspace, is the project screen for answering, "what is happening here right now?" Use the lens buttons at the top to switch between event quality, errors and logs, performance, monitors, and custom app metrics. Then narrow the view with time range, environment, release, and attribute filters before opening the recent stream.

Good dashboard recipes

• Release validation: filter to the new release, add total events, errors, transaction P95, and database query average, then compare the last hour with the previous day.
• Instrumentation audit: use the metric catalog, recent stream, and performance page to confirm logs, custom metrics, transactions, spans, and check-ins are arriving from the expected service or environment.
• Performance triage: add transaction P95, database query P95, request load spans, and error count so slowdowns and new failures share one timeline.
• Operational monitoring: filter by job or queue attributes and add custom metric series such as queue depth, processed jobs, retry count, or worker latency.

Why some filters or charts may look empty

Charts can only filter and plot values that your app sends consistently. If environment or release menus are empty, the incoming events probably do not include those labels yet.

• Use stable values such as service, region, queue, route, or tenant_tier.
• Avoid raw IDs, emails, full URLs, and request bodies as chart dimensions.
• Keep custom metric names stable and send a numeric value when you want a value chart instead of just a count.
• Use faster live refresh only while actively watching a deploy or incident.

Recent stream

Use the stream after the chart has been narrowed.

• FilterChoose the time, release, environment, and attribute slice first.
• ConfirmCheck that the newest matching events have the labels you expect.
• InspectOpen one row to move from trend-level signal into event detail.

Project lifecycle

Archive projects when you want history, delete only when you mean it.

Project lifecycle controls live in Settings because they change where the project appears in the UI. Archive is the reversible choice: the project leaves active dashboards and menus, but you can still find its history from archived views. Delete is the permanent choice and should only be used when the project and its history should disappear from the product.

Triage errors

Use Issues to decide what needs attention.

Issues shows grouped errors, not every repeated event. Use search when you know the message or fingerprint, the assignee menu when you are dividing work, and the status chips when you want open, introduced-today, resolved, ignored, archived, or all groups. The selected group opens on the right so you can act without leaving the list.

New to triage? Open the ? menu on Issues and choose Triage your first issue. It walks through one of the project's real open issues: read the issue, check what shipped, assign an owner, and close the loop. The choices you make change the issue for real, and you can leave at any step without changing anything you have not chosen.

Investigate faster

Open an issue and see the context around it.

The event detail pane is designed for the moment after you ask, "what happened here?" It combines payload context, stack or runtime details, occurrence history, and nearby logs that share the same trace, request, session, or user identifiers. Error details keep the main issue content in fixed-height panes so large payloads or long stack traces can scroll without pushing the rest of the workbench away.

If related logs or release context are missing, the event may not include enough shared identifiers yet. Environment and release labels help you compare deploys. Trace, request, session, and user identifiers help Logister connect an error to nearby logs and repeated occurrences.

Connected projects · Logister 3.8+

Follow a mobile failure into its backend request.

Connect the app and backend from Settings > Connections with explicit environment mappings, enable related requests on the instance and both projects, and propagate request identifiers with a supported SDK. A connection grants no access; readers must already have access to both projects.

Reports inspect up to 500 recent anchor records over at most seven days and show partial coverage. Peer counts include matching records only; installation and session counts stay within each mobile project. Observed matches and before/after counts do not prove cause or total traffic.

Issue JSON exports can optionally include connected evidence. Existing error emails resolve related records using the recipient's current access. Read connection setup and connected impact and its limits before using this workflow.

Understand performance

Turn transactions and metrics into a project performance view.

The project Overview gives you a quick read before you open deeper views. Use the timeline to see whether activity changed, the error group summary to see whether issues need review, and the request timing cards to decide whether latency deserves attention. The Performance tab holds the detail.

• Transaction cards show volume, throughput, P50 latency, P95 latency, error rate, and Apdex for recent traffic.
• Slow transaction rows highlight the slowest recent work and link to related errors when they share transaction context.
• Database load appears when your app sends database timing metrics such as db.query.

Releases

Check what shipped, and what each release changed.

Releases > Deployments lists the deployments recorded for the project from CI, the CLI, or the HTTP API, with repository, environment, source, and search filters. Release health, below the list, shows each recent release with its total events, error events, introduced issues, and regressed issues when your events include a release name.

• Android and iOS projects also have Releases, the builds observed in telemetry, and Artifacts, where you upload R8 mappings or dSYMs and see which builds they cover. Deploy records appears once a mobile project has recorded deployments.
• If a release shows regressed issues, open Issues and filter to open groups; a regressed issue is one that was closed and has come back.

Watch scheduled work

Use check-ins for cron jobs, workers, and recurring tasks.

Scheduled work often fails quietly. Logister check-ins let each job report a slug, status, environment, expected interval, optional release, and duration. The Monitors tab, which appears once the project has a monitor, shows whether recent jobs are ok, in error, or missed based on the interval you set.

Review activity

Keep non-error telemetry visible too.

Explore › Events is the project activity feed. Use the type, period, environment, release, and search filters when you want to confirm that a signal arrived, find a specific log or metric, or open a non-error event with the same detail tools used for errors. Explore › Archive searches older telemetry and the archive runs that may hold it.

Email notifications

Send useful alerts without turning every occurrence into mail.

Notification settings are split by purpose so users do not have to understand every option at once. Start at Project > Settings > Notifications, choose the path that matches the reason for email, then tune that path only.

Work with teammates

Share project visibility without sharing every account credential.

Project owners and project admins share access with existing, confirmed Logister users by email in Settings > Team, which also shows unresolved assignment counts beside members. Pick a role when you share:

Members are not read-only: triage changes are visible to everyone and can send notifications. If you share a project only so someone can look, tell them which issues they own. The Member role was previously labelled Viewer; existing shares keep the same permissions.

Admins can also use the admin area for account-level user cleanup and confirmation work when the instance is configured to grant them access.

Run it yourself

Use product settings for project-level decisions.

Most users only need the project UI: Setup for connecting an app, Issues for triage, Explore for review, and Settings for notifications, team access, and data cleanup. Instance-level setup lives in the operations docs so product pages can stay focused on what users see and choose inside Logister.

For project-level cleanup behavior, read the data retention guide. It explains what the Settings > Data choices mean before you change retention windows or archive settings.

Where to go next

Pick the guide that matches what you are trying to do.