On Thu, Aug 27, 2020 at 02:04:20 +, Daan van Gorkum wrote:
> Hi Jeff,
>
> Thanks again for your insights. I understand that a lot of features are
> pending and it's totally fine, we're just very eager to use all these
> features.
I completely forgot that the work to add those fields was done
: Josef 'Jeff' Sipek
Sent: 26 August 2020 23:02
To: Daan van Gorkum
Cc: Dovecot Mailing List
Subject: Re: Metric label values truncated when using OpenMetrics endpoint
On Tue, Aug 25, 2020 at 01:08:06 +, Daan van Gorkum wrote:
> Hi Jeff,
>
> Thanks for your reply!
>
On Tue, Aug 25, 2020 at 01:08:06 +, Daan van Gorkum wrote:
> Hi Jeff,
>
> Thanks for your reply!
>
> Regarding grouping by remote address, I understand and for now I'll keep a
> close eye. Maybe it's an option to group by /24 for ipv4 and /64 for IPv6?
Hrm, interesting idea. But the answer
tended but they do not contain any information about the connecting client.
Thanks again!
Daan
From: Josef 'Jeff' Sipek
Sent: 24 August 2020 20:47
To: Daan van Gorkum
Cc: Dovecot Mailing List
Subject: Re: Metric label values truncated when using Open
On Sat, Aug 22, 2020 at 00:31:36 +, Daan van Gorkum wrote:
> Hi,
>
> Recently we upgraded to Dovecot 2.3.11.3 and configured an example metric
> like this:
>
>
> metric imap_command {
> event_name = imap_command_finished
> group_by = cmd_name tagged_reply_state user remote_ip
Grouping b
Hi,
Recently we upgraded to Dovecot 2.3.11.3 and configured an example metric like
this:
metric imap_command {
event_name = imap_command_finished
group_by = cmd_name tagged_reply_state user remote_ip
}
And enabled the OpenMetrics listener like this:
service stats {
inet_listener http {
