Skip to content

fix(log-management): update access logs formats to clever-tools v4#973

Open
hsablonniere wants to merge 1 commit into
mainfrom
fix/accesslogs-clf-doc
Open

fix(log-management): update access logs formats to clever-tools v4#973
hsablonniere wants to merge 1 commit into
mainfrom
fix/accesslogs-clf-doc

Conversation

@hsablonniere

@hsablonniere hsablonniere commented Jun 24, 2026

Copy link
Copy Markdown
Member

Context

Reported in clever-tools#909: the Access logs section of log-management.md is out of date. It still describes the Warp10-era clever accesslogs:

  • formats simple and extended no longer exist (the CLI now uses human, json, json-stream, and clf)
  • the CLF example shows a stray - for the missing HTTP protocol ("GET / -")
  • the JSON sample uses the old short-key payload (ipS, vb, bOut…) instead of the v4 access log shape

Proposal

Rewrite the section to match the current CLI output:

  • human (default), clf, json, json-stream
  • CLF request line reduced to method path — the protocol version is absent from the v4 payload, and a - placeholder breaks structured parsing in grok/GoAccess (see clever-tools PR #1104)
  • JSON example updated to the real v4 ApplicationAccessLog object

Paired with clever-tools PR #1104, which restores the clf format in the CLI.

The access logs section still documented the Warp10-era CLI: the `simple` and
`extended` formats no longer exist, the CLF example carried a stray `-` for the
missing protocol, and the JSON sample used the old short-key payload.

Align it with the current `clever accesslogs` output: `human` (default), `clf`,
`json` and `json-stream`, with the v4 access log JSON shape and a CLF request
line reduced to `method path`, as reported in clever-tools#909.
@github-actions

github-actions Bot commented Jun 24, 2026

Copy link
Copy Markdown

✅ Review app deployed

Check how your changes look like!

ℹ️ Name 🔗 Infos & links
🌱 Latest deployed commit 72b9107
👁️ Preview https://documentation-PR-973.cleverapps.io/developers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant