LogsAsEventStreams [rule] v1.0.0

The app writes its event stream, unbuffered, to stdout. It does not concern itself with routing or storage. The execution environment captures the stream and routes it to log indexers, archives, or analytics. Log files in the app are an anti-pattern because they are local, finite, and rotate-coupled to disk.

Checks

• console.log / fmt.Println / logger output goes to stdout. No log.txt in the repo.
• Lines are unbuffered: a crash should not lose recent log lines.
• Structured (JSON) logs are encouraged so the platform indexer can parse fields.
• Log routing (to ELK, Datadog, Cloud Logging) is configured at the platform layer, not in app code.

Label

Treat logs as event streams written to stdout

LogsAsEventStreams [rule] v1.0.0

The app writes its event stream, unbuffered, to stdout. It does not concern itself with routing or storage. The execution environment captures the stream and routes it to log indexers, archives, or analytics. Log files in the app are an anti-pattern because they are local, finite, and rotate-coupled to disk.

Checks

• console.log / fmt.Println / logger output goes to stdout. No log.txt in the repo.
• Lines are unbuffered: a crash should not lose recent log lines.
• Structured (JSON) logs are encouraged so the platform indexer can parse fields.
• Log routing (to ELK, Datadog, Cloud Logging) is configured at the platform layer, not in app code.

Label

Treat logs as event streams written to stdout

Label

Treat logs as event streams written to stdout