Static sites
One line for every request the site served, with host, path, status, size and timings.
- Sent once the site has an address
Send the access logs of your sites and the output of your apps to a log collector that runs on your realm, or to your own Loki or HTTP endpoint.
Loki or HTTP
on every paid plan
1 to 365 days
30 days unless you change it
Grafana
or the search in the panel
Attach a destination from the page of whatever you want logs from. Nothing is sent until you attach one.
One line for every request the site served, with host, path, status, size and timings.
Everything the app’s container prints.
An app started through webappmk-client ships its output to the destinations attached to its config.
A container app shows its latest output on its Logs tab, with no destination needed.
A Loki-compatible collector that runs on your realm as a resource of its own, with storage of its own.
Creating a collector also creates its log destination, already verified, so sites and apps can be attached right away.
Every push and every query carries the collector’s key in the X-Scope-OrgID header. The edge refuses any other key.
Ship logs from servers outside the platform with Grafana Alloy, Vector, Fluent Bit or anything that pushes to the Loki API.
Add the collector to Grafana as a Loki data source with the key as a header, or query it with logcli.
Search the last 5 minutes to 24 hours by text, for sites, apps or everything. Up to 100 lines, five searches a minute.
Keep logs from 1 to 365 days. Storage starts at 1 GB and grows in 0.5 GB steps up to 50 GB. It never shrinks.
Use a Loki you already run, or any HTTP endpoint that accepts NDJSON.
A Loki push URL with an optional tenant, or an HTTP endpoint that receives one JSON object per line.
None, a login, a bearer token or a header of your own, typed in or taken from your secrets. A CA or client certificate can be added.
A test entry carries a one-time link. Open it from your own log viewer to prove the logs arrive where you can read them. Only a verified destination can be attached.
Changing the address or the credentials clears the check until a new test entry is confirmed. Whatever is attached keeps shipping meanwhile.
See what every service said around the minute something broke.
See what visitors ask for, what fails and which bots come by.
Logs from the platform and from your own servers in one place.
The collector speaks the Loki API, so the usual shippers and viewers work with it.
Run any Docker image with a private network, persistent volumes and a port on your domain.
Publish a static website from GitHub, any Git repository or a zip archive. It is served over HTTPS.
Keep variables, secrets and feature flags out of your code. Your app fetches them when it starts, wherever it runs, and changes reach it without a redeploy.