Demo
Demo

Knowledge base

PMTA knowledge base›Block <signals>›Directive§ 11.1.6.2.14

log-verbose

<signals>

Detailed logging of the export to the vendor's analytics
in the configuration this is a linelog-verboseinside the block <signals>
Why events do not reach the vendor’s analytics

The line adds to the log the course of the event export to external analytics. The default is off.

The same technique as for the accounting webhook. Export faults have one symptom — events do not appear on the other side — and many causes: the key, the address, the network, the format.

By default only errors are written. The line adds messages about normal operation and makes error entries more detailed.

The main trap is leaving it on after the investigation. The line breaks nothing and therefore outlives the investigation: the log grows, rotation speeds up, and last week’s entries are pushed out before they are needed.
What the Hub does. It does not write it and does not use export to external analytics: fleet events come to us directly, via the accounting webhook.

The line is worth knowing when investigating someone else’s node where such an export is configured.

Recommended values

Enabled for the duration of an investigation and turned off afterwards:

Value When
no (default) normal operation
yes events do not appear in the external analytics
The default and the subject of the record come from the manual (§ 11.1.6.2.14). The order of investigation and the warning about volume are ours.
Example configuration
# for the duration of the investigation
<signals …>
    log-verbose true</signals>
After the investigation the line is removed. With edits through the Hub it will disappear anyway at the next configuration apply.
yellow — — directive names, blue — blocks. They are highlighted the same way in the text of the card.
▲

Common mistakes and problems

what people get wrong and how it ends2 mistakes▶

Leaving it on after the investigation

our experience

What it costsUnder load the export runs constantly, and detailed logging noticeably adds to the log’s volume.
How to spot itThe log grows faster than usual for no visible reason.
How to do it rightReturn the off value after the investigation.

Looking for these entries in the accounting file

our experience

What it costsThe log and accounting are different files and different questions. Accounting has the result per message, but not the course of the node’s work.
How to spot itThere is nothing resembling the expected entries in the accounting file.
How to do it rightLook at the log whose path is set by the log-file line.
Compatibility
PowerMTA 6.0
described in the manual of this version · platform: any
The vendor does not state the first version for every directive — there is no note here. The name also appears in the 5.0 edition of the manual.
Reference data
Syntax
log-verbose { yes | no }
Values
yes | no | true | false
Default
§ 11.1.6.2.14
Applying
reload, no restart needed
Queue
will not touch what is already queued
Where to write it
<signals>
How many times
once in the block
Everything here comes from the manual, with the section.
Inheritance
No inheritance: the line lives inside its own <signals> and concerns only it. The log, meanwhile, is one per node — entries from all enabled switches land in it intermixed.
⇄

Related directives

1 relation

Applies to

log-fileGlobalThe entries go into the very log set there. inference

How to check on the node
We look at the engine log, filtering the relevant lines:
grep -i "signals" /var/log/pmta/log | tail -20
Messages about export attempts and reply codes will appear. Nothing means the export is not configured or does not start at all.
◇

What else to read

3 articles

◇What the node tells about itself and through which channelsSeven observation surfaces: the web monitor, the console in four formats, the log, accounting, accounting search, metrics and export to external analytics.◇The watchdog that restarts the engineKeeps an eye on the engine and brings it back up after a crash by itself, sending a crash report to the postmaster address.◇What makes a virtual machine riskyRunning on a virtual machine is possible, but the manual does not recommend it without sufficient hardware and properly tuned hypervisor settings: under load the node may stop responding.

In the Hub
Cost of a mistake
safe: a wrong value breaks nothing
Scenarios
Untangle a stuck queue
Neighboring settings of the block <signals>:privacy-policyhtml-edit-error-modecustom-message-id-headerretain-x-sp-subaccount-idengagement-trackingAll 16 directives of the block →