Logging

Controls log levels and logging destinations.

Logging Configuration

Key	Type	Required	Description
`components`	Map of Component Name to Component Config	No	Logging component configuration. See Component Names for common component names.
`rotation`	Log Rotation	No	Log file rotation configuration for all configured `components`. Available since 1.4.2

Component Config

Key	Type	Required	Description
`level`	enum	No	Log level, from most to least verbose: `Trace`, `Debug`, `Info` (default), `Warn`, `Error`, `Fatal`, or `Panic`.
`log_path`	string	No	If specified, component will be written in `json` format to a file at this path. Default is to write the log to `stdout` in human-readable format.
`log_file_mode`	uint32	No	If `log_path` is specified and the file does not exist, this is the mode the file will be created with. Default is `0o600`.

Component Names

Component	Description
`agent`	Monitoring agent and communication with NATS Systems
`alerting`	Alerting evaluation and notification dispatch
`api`	API request logs
`app`	Application startup and shutdown process
`audit`	Audit log for API requests. See Audit Logging
`audit_service`	Audit log collection from managed NATS systems
`auth`	Authentication request logs
`catalog`	Synadia Catalog platform component service
`encrypter`	Data encryption and KMS key access
`health`	System and data plane health checks
`internal_events`	Internal event bus over the control plane NATS connection
`internal_nats`	Internal NATS connection used by the control plane
`internal_postgres`	Internal PostgreSQL process, if enabled
`internal_prom_db`	Internal Prometheus time-series database
`internal_prometheus`	Internal Prometheus process, if enabled
`internal_prometheus_metrics`	Internal Prometheus metrics collection service
`last_active`	Tracking of last-active timestamps for entities
`metrics`	Metrics server for managed NATS systems
`nats_api`	NATS API (data plane) request logs
`oidc`	OIDC authentication provider integration
`release_monitor`	Monitoring of available data plane releases
`scraper`	Metrics and status scraping from managed NATS systems
`schema_registry`	Synadia Schema Registry platform component service
`sql`	SQL database migrations
`sys_connect`	Connection management to managed NATS systems
`ui`	Web UI serving and configuration
`version_monitor`	Monitoring of managed NATS system versions
`workloads`	Synadia Workloads platform component service

Log Rotation

Key	Type	Required	Description
`max_size_mb`	int	Yes	Log file will rotate once configured size is reached.
`max_age_days`	int	No	If specified, rotated log files will be deleted once this age is been reached. Default is `0` (unlimited).
`max_backups`	int	No	If specified, oldest rotated log file will be deleted once this quantity of rotated log files is reached. Default is `0` (unlimited).
`compress`	bool	No	If true, rotated log files will be compressed with gzip compression. Default is `false`.

Audit Logging

Audit logging records the following fields:

time: Time
authorized: true or false
authorization_decision_data: Data from authorization engine
authenticated: true or false
authentication_method: SESSION or BEARER
entity: Entity type
operation: CREATE, READ, UPDATE, or DELETE
request_id: Unique ID for HTTP request
request_method: HTTP Method
request_remote_addr: HTTP Remote IP/Port
request_user_agent: HTTP User Agent Header
request_url: HTTP URL
request_x_forwarded_for: HTTP X-Forwarded-For Header
session_id: Session ID
result: SUCCESS or FAILURE
response_status: HTTP Response Status Code
user_id: User's database ID
user_identifier: User's Username or Email
user_name: User's Name

By default, audit logging runs at Info level, logs to stdout in human readable format, and only logs CREATE, UPDATE, and DELETE operations. To enable audit logging for READ operations also change it to Trace level.

Example: write all operations to an audit log file at /var/log/scp-audit.log in json format:

logging:
  components:
    audit:
      level: Trace
      log_path: /var/log/scp-audit.log
      log_file_mode: 0o644