; Log to stdout only — Docker's json-file driver captures it and the host
; Alloy ships it to Loki as job=<compose project>. Writing to a file inside
; the container would put the logs where nothing can see them.
[general]
dateformat = %F %T
; Colour is disabled in asterisk.conf (`nocolor = yes`), not here — Asterisk
; colourises the console by default and the escape codes travel through Docker
; into Loki, where every line arrives wrapped in \x1b[0;30m. That file must be
; mounted for the setting to take effect.

[logfiles]
; `notice` is KEPT, deliberately. Asterisk logs rejected SIP requests at
; notice level via log_failed_request ("No matching endpoint found",
; "Failed to authenticate"), and on a box whose whole job is answering SIP
; those are the single most useful diagnostic. Dropping notice made the log
; quieter and the gateway undebuggable — a call was refused and nothing said
; so.
;
; `verbose` is excluded: dialplan execution ("Executing [1001@...]") is
; useful when tracing a specific call, but it is not worth shipping to Loki
; continuously. Raise it at runtime instead:
;     asterisk -rx "core set verbose 3"
;
; The healthcheck's "Remote UNIX connection" pairs also arrive on notice.
; They are dealt with at the source rather than by silencing the channel:
; docker-compose replaces the image's ~7-connections-per-30s healthcheck with
; a single check on a 60s interval, and modules.conf stops the container
; loading hardware and database modules it has no use for (~74 ALSA lines per
; restart). Those two together cut the noise without costing visibility.
console => notice,warning,error