Hi,
we found the failure, it works now,
we disabled the stats_writer_socket (i dunno why exactly, hopefully some
legacy s***)
thanks for your help
Kind regards
Marcel
On 23.07.24 16:11, Marcel Schmidt via dovecot wrote:
Hi,
still no luck
all duration 0 0 0 0 0.00 0
0.00 0
seems it has something todo with our setup,
i cant think of anything else
i will test in another testing environment
Kind regards
Marcel
On 23.07.24 15:59, Aki Tuomi via dovecot wrote:
event_exporter log {
format = json
format_args = time-rfc3339
transport = log
}
metric all {
filter=event=*
exporter=log
}
On 23/07/2024 16:56 EEST Marcel Schmidt via dovecot
<dovecot@dovecot.org> wrote:
Hi Aki,
still no output, i think i have to dig more.
Is there any possibility to see, what events my dovecot server is
"logging"?
We have a construct like proxy -> director -> storagenode
i guess not every server in that construct has the same events, so I
could
just be unlucky.
Kind regards,
Marcel
On 23.07.24 15:50, Aki Tuomi via dovecot wrote:
On 23/07/2024 16:34 EEST Marcel Schmidt via dovecot
<dovecot@dovecot.org> wrote:
Hi,
i have the exact same problem, i configured everything as said in the
documentation, but the output is always 0
metric client_connections {
filter = event=client_connection_finished
}
metric auth_success {
filter = (event=auth_request_finished AND success=yes)
}
metric mail_delivery {
filter = event=mail_delivery_finished
}
doveadm stats dump
metric_name field count sum min max avg
median stddev
%95
client_connections duration 0 0 0 0
0.00
0 0.00 0
auth_success duration 0 0 0 0 0.00 0
0.00 0
mail_delivery duration 0 0 0 0 0.00 0
0.00 0
do i have to enable stats in mail_plugins? I thought this is only
the case if i would want to use the
old stats module, but even when i enable it, it doesnt work:
doveadm stats dump
Fatal: Plugin 'stats' not found from directory
/usr/lib/dovecot/modules
Dovecot version 2.3.18 (Ubuntu)
You don't have to enable old_stats plugin, it's only needed for old
stats.
Not entirely sure why you are not seeing those events, you should
first verify that the stats socket is writable.
service stats {
unix_listener stats {
mode = 0666
}
}
Aki
_______________________________________________
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
_______________________________________________
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
_______________________________________________
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
_______________________________________________
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
_______________________________________________
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
