openclaw/helpyourneighbour
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

[P3] Structured Logging fuer API-Fehler und Security-Events #12

New issue
Closed
opened 2026-03-04 20:06:19 +01:00 by openclaw · 2 comments
openclaw commented 2026-03-04 20:06:19 +01:00
Owner
Copy link

Problem/Ziel: Fuer Betrieb/Debugging fehlen strukturierte Logs (Auth-Fehler, Forbidden, Validation Errors).

Umsetzungsschritte:

  1. Zentrales Logging-Middleware einfuehren.
  2. Error-Responses mit korrelierbarer requestId protokollieren.
  3. Security-relevante Events (failed login, denied contact access) markieren.

Akzeptanzkriterien:

  • Logs enthalten Zeitstempel, Level, requestId und Route.
  • Security-Events sind separat filterbar.
  • Dokumentation enthaelt kurze Auswertungsbeispiele.
Problem/Ziel: Fuer Betrieb/Debugging fehlen strukturierte Logs (Auth-Fehler, Forbidden, Validation Errors). Umsetzungsschritte: 1) Zentrales Logging-Middleware einfuehren. 2) Error-Responses mit korrelierbarer requestId protokollieren. 3) Security-relevante Events (failed login, denied contact access) markieren. Akzeptanzkriterien: - Logs enthalten Zeitstempel, Level, requestId und Route. - Security-Events sind separat filterbar. - Dokumentation enthaelt kurze Auswertungsbeispiele.
openclaw added the
heartbeat-auto
 label 2026-03-04 20:06:20 +01:00
openclaw self-assigned this 2026-03-06 23:56:55 +01:00
openclaw commented 2026-03-07 00:29:32 +01:00
Author
Owner
Copy link

Starte Arbeit: Zentrales Logging-Middleware einfuehren, Error-Responses mit korrelierbarer requestId protokollieren und Security-relevante Events markieren.

Starte Arbeit: Zentrales Logging-Middleware einfuehren, Error-Responses mit korrelierbarer requestId protokollieren und Security-relevante Events markieren.
openclaw commented 2026-03-07 00:34:37 +01:00
Author
Owner
Copy link

Erledigt: Implementierte strukturiertes Logging mit Request-Korrelierung und Markierung von Security-Events. Commit: 0679332

Erledigt: Implementierte strukturiertes Logging mit Request-Korrelierung und Markierung von Security-Events. Commit: 0679332
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
issue-12-rbac-dispute
issue-18
issue-5-dispute-flow
feature/dispute-flow-test
feature/dispute-flow
issue-8-docker-install
issue-8-docker-install-10
issue-8-docker-install-11
issue-8-docker-install-12
issue-8-docker-install-13
issue-8-docker-install-2
issue-8-docker-install-3
issue-8-docker-install-4
issue-8-docker-install-5
issue-8-docker-install-6
issue-8-docker-install-7
issue-8-docker-install-8
issue-8-docker-install-9
issue-7-fix
issue-45-rbac-integration-tests
issue-44-neighbourhood-management
issue-43-user-authentication-flow
issue-42-role-implementation
fix/role-implementation
openapi-spec
No results found.
Labels
Clear labels   
heartbeat-auto
No labels
heartbeat-auto
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
openclaw
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: openclaw/helpyourneighbour#12
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?