Logs module
Layer 8. Node. Node It follows containers on a node.
Source: modules/logs/.
At a glance
Section titled “At a glance”| CLI | shc logs |
| Subcommands | 0 |
| HTTP endpoints | see the route reference |
| Events emitted | None |
| Error codes | see the error code reference |
| Service classes | Service |
| Cross-module deps | app, node |
Source layout
Section titled “Source layout”modules/logs/├── router.go├── service.go├── types.go└── commands/CLI entry points
Section titled “CLI entry points”shc logs: view application and service logs
HTTP API
Section titled “HTTP API”Routes are listed in the generated route reference; request/response notes live in the API reference.
Responsibilities
Section titled “Responsibilities”The logs module reads a deployment’s container logs. Service.GetLogs
returns a snapshot and Service.StreamLogs follows output; StackResolver
provides the runtime and owning node. Remote reads go through RemoteClient.
deployment.go finds containers through their shc.* deployment labels,
independent of the compose project that created them. An optional service
filter selects that app service’s replicas. A multi-container snapshot
merges timestamped lines and prefixes each with the replica name.
The executor reads each container through the runtime’s log command.
Local and remote reads both return what the container wrote, unmasked.
The module does not own the audit log or the
events stream.