301005Re: Connection stats
- Jul 14, 2014On 7/14/2014 8:25 AM, Wietse Venema wrote:
> In response to Noel's followup, here is a proposal that can makeSeems to me an error count, including unknown commands, would be
> Postfix trouble shooting / anomaly detection easier. This would
> reveal information that is currently available only by turning on
> verbose logging.
> The Postfix SMTP server maintains two counters for each known
> command: one counter for the total number of times the command was
> issued during an SMTP session, and one counter for the number of
> normal completions (a 2XX reply status). These counters are reset
> before the server accepts the next SMTP connection. Perhaps there
> should also be a counter for unknown commands.
Or unknown commands/total errors maybe? err=n/T
This would not be logged if there are no errors.
> Upon disconnect. the Postfix SMTP server logs statistics for each
> command that has a non-zero counter. The syntax is:
> Example: a "normal" session with ESMTP handshake, one mail delivery
> transaction with one recipient, and closed with "quit":
> ehlo=1/1 mail=1/1 rcpt=1/1 data=1/1 quit=1/1
> The logging shows only counters for commands that were actuallyI vote for consistent 1/1. But I don't feel strongly about it.
> issued. To save space we could replace "n/n" (two identical numbers)
> with just "n". I don't know if this would actually simplify parsing.
> As the examples show this is really a small amount of text, so there
> is no reason to increase logging overhead by using a separate record.
> Since the stats would be logged at the end of a session, they can
> be logged in the "disconnect" record.
-- Noel Jones
- << Previous post in topic Next post in topic >>