webapp.mk
Features

Logs and log collector

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.

Logs and log collector

How it works

  1. Sites and apps
  2. A log destination
  3. Collector or your endpoint
  4. Grafana or a search
Destinations

Loki or HTTP

on every paid plan

Log collector keeps

1 to 365 days

30 days unless you change it

Read with

Grafana

or the search in the panel

Plans with a log collector

Logs and log collector

What sends logs

Attach a destination from the page of whatever you want logs from. Nothing is sent until you attach one.

Static sites

One line for every request the site served, with host, path, status, size and timings.

  • Sent once the site has an address

PHP, WordPress and container apps

Everything the app’s container prints.

Apps on your own servers

An app started through webappmk-client ships its output to the destinations attached to its config.

Recent output in the panel

A container app shows its latest output on its Logs tab, with no destination needed.

Logs and log collector

The log collector

A Loki-compatible collector that runs on your realm as a resource of its own, with storage of its own.

Ready to attach

Creating a collector also creates its log destination, already verified, so sites and apps can be attached right away.

A tenant key

Every push and every query carries the collector’s key in the X-Scope-OrgID header. The edge refuses any other key.

  • The key cannot be changed without losing what is stored

Push from anywhere

Ship logs from servers outside the platform with Grafana Alloy, Vector, Fluent Bit or anything that pushes to the Loki API.

Read in Grafana

Add the collector to Grafana as a Loki data source with the key as a header, or query it with logcli.

Search in the panel

Search the last 5 minutes to 24 hours by text, for sites, apps or everything. Up to 100 lines, five searches a minute.

Retention and storage

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.

Logs and log collector

Your own destination

Use a Loki you already run, or any HTTP endpoint that accepts NDJSON.

Loki or HTTP

A Loki push URL with an optional tenant, or an HTTP endpoint that receives one JSON object per line.

Authentication

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.

Verified before use

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.

Re-checked after a change

Changing the address or the credentials clears the check until a new test entry is confirmed. Whatever is attached keeps shipping meanwhile.

Logs and log collector

Who it is for

Developers

See what every service said around the minute something broke.

Site owners

See what visitors ask for, what fails and which bots come by.

Teams

Logs from the platform and from your own servers in one place.

  • Debugging a release
  • Access logs
  • Error hunting
  • Traffic review
Logs and log collector

Standard tools

The collector speaks the Loki API, so the usual shippers and viewers work with it.

Read with

  • GrGrafana
  • lologcli
  • SeSearch in the panel

Ship with

  • GrGrafana Alloy
  • VeVector
  • FlFluent Bit
  • wewebappmk-client

Destination types

  • LoLoki
  • HTHTTP with NDJSON

Start with a free static site

Add resources when you need them.