Monitoring

Reads the log of a lambda

Its requests, what its code printed, and what the server said while serving it - a handler that threw, a request that timed out. Oldest first. To follow it, pass the cursor of each answer as since of the next; missed says how many lines went by unread in between. Requests are logged as warnings when they were answered with a client error and as errors with a server error. The previews of its features have logs of their own.

get/lambdas/{privateKey}/logs

Request

  • Base URL: https://genhttp.dev/api/v1
  • URL: https://genhttp.dev/api/v1/lambdas/{privateKey}/logs
  • Auth: none declared

Path parameters

privateKeystring required

The editor key of the lambda. Holding it is what allows the call.

Query parameters

sinceinteger

The cursor of the previous answer: only what came after it. Left out, the last 500 lines.

levelstring

The lowest level to answer with: debug, info (the default), warn or error

limitinteger

At most this many lines, up to 2000; by default 500, or 1000 with since

Response

The lines, and where to carry on from

Cursorinteger

The newest sequence held; pass it as since to read what comes after

Missedinteger

Lines that were dropped before this reader got to them, because the ring went round or more matched than were asked for

Capturingboolean

Whether what lambdas print is kept at all on this installation

Changes

No recorded changes to this operation across all 1 revision of this API.