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
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_e
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
> wrote:
>
>
> Hi Aki,
>
> still no output, i think i have to dig more.
> Is there any possibility to se
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,
M
> On 23/07/2024 16:34 EEST Marcel Schmidt via dovecot
> 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
Please see https://doc.dovecot.org/configuration_manual/stats/
how to configure 2.3 stats.
Aki
On 08/06/2024 00:28 EEST Adam Miller via dovecot
wrote:
Hello again everyone! I am trying to get the “doveadm stats dump”
command to work and even though it does not
