How-to Guides: Setup, Logs, Alerts & Upgrading
Step-by-step guides with screenshots for Midline: create a project, connect NestJS, React, Go, Express, Swift or Python, read logs and traces, set up alerts.
Guides
- Create an organisation: An organisation is the workspace that owns your projects, team members, billing plan and alert rules. Create one for each company or client you monitor. PDF
- Create a project: A project is one app or service: your API, your web app or a background worker. Each project has its own API keys, logs, issues and traffic rules, so give each one its own. PDF
- Set up a NestJS project: Add the Midline agent to a NestJS API as middleware. It records every request, error and (optionally) console line, and never sits in the request path. PDF
- Set up an Express project: Two lines of middleware give an Express app request logs, error tracking and live streaming. If you cannot change the code, run the agent as a proxy in front of it instead. PDF
- Set up a React project: Add the browser SDK to a React app to capture uncaught errors, failed network calls and Web Vitals, using a public key that only works from the sites you list. PDF
- Set up a Go project: Go has no Midline package yet, and does not need one: your service reports each event with one HTTP POST, sent from a goroutine so it never slows a request. PDF
- Set up a Python project: Report requests and errors from Django, Flask, FastAPI or a plain script with one HTTP POST, sent from a background thread so it never slows your code down. PDF
- Set up a Swift (iOS) project: There is no Midline iOS SDK yet, and that is deliberate: a secret key inside an app binary can be read by anyone who unpacks it. Here is what to do today. PDF
- Watch request logs: The Logs page is a live tail of every request your project handles: method, route, status, duration and caller IP, streamed as it happens and searchable back through your plan’s history. PDF
- See your visitors: The Visitors page counts the people using your web app over time, lists the sessions that were most recently active with the address each connected from, and shows where visitors drop off on the way to a goal. PDF
- Watch terminal logs: Terminal is a live view of what your app prints: console.log, framework loggers, warnings and stack traces, streamed from your servers or browsers as if you were tailing the process. PDF
- Watch traces: A trace follows one action from the browser to your backend and back: every call, error and log line that shared the same trace id, laid out on one timeline. PDF
- Watch issues: Issues turns a flood of failures into a short list. Errors, 5xx responses and security events are grouped by fingerprint, so one underlying bug is one row, however many times it happens. PDF
- How to upgrade your plan: Move from Starter to Basic or Pro when you need more organisations, projects, team members or log history. Checkout runs on Paystack’s hosted page, so Midline never sees your card details. PDF
- Monitors, alerts and traffic control: Three tools that watch for trouble so you do not have to. Monitors check that your endpoints and scheduled jobs are alive, alert rules decide who hears about it and where, and traffic control flags or blocks unwanted requests. PDF
- Set up API keys and source maps: API keys decide which project your events land in. Source maps turn minified stack traces from your web app back into the code you wrote. PDF
- Set up notification preferences: Who gets emailed, and about what? Three places control it: the organisation’s email switch, your alert rules, and the notifications tab in your personal preferences. Here is what each one does. PDF