Marcos Silva
25 lines
1.2 KiB
Markdown
25 lines
1.2 KiB
Markdown
---
|
|
name: gfiber-logging
|
|
description: Decide and review GFiber service log levels while keeping production INFO output bounded and traceable. Use when adding, changing, or auditing service logs.
|
|
---
|
|
|
|
# gfiber-logging
|
|
|
|
## Inputs
|
|
Changed paths or service root, the request or flow under review, and the project logging configuration.
|
|
|
|
## Workflow
|
|
1. Read `references/levels.md` to classify each event; use `references/cases.md` for known service patterns.
|
|
2. Check new lines for correlation, minimized fields, and bounded volume.
|
|
3. Use `references/audit.md` for a static audit; measure representative traffic separately when a path is high-volume.
|
|
4. Report each finding with evidence and distinguish measured results from risk estimates.
|
|
|
|
## Rules
|
|
- Use the approved contextual logger when the project supports one.
|
|
- Never log secrets, PII, or full request/response bodies; cap identifier lists.
|
|
- Treat INFO caps and DEBUG deployment settings as project configuration facts. Report missing evidence rather than assuming them.
|
|
- This skill is read-only. Do not edit code or production configuration.
|
|
|
|
## Output
|
|
State the scope, each finding (location, level, reason, volume risk, action), audit command/results, and any unmeasured risk.
|