<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hi Jeff, <br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thanks for your reply!</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
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? We currently do that based on the logs but the
<span class="ITWTqi_23IoOPmK3O6ErT">OpenMetrics endpoint</span> seem a lot easier.</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
A slight hijack of the original question: but I tried to log only IP addresses (+ result) of failed login attempts but it seems I cannot find a metric that would contain that information. Am I looking in the wrong direction? The auth_userdb_request_finished
and auth_passdb_request_finished stats work as intended but they do not contain any information about the connecting client.
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thanks again!</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Daan<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Josef 'Jeff' Sipek <jeff.sipek@open-xchange.com><br>
<b>Sent:</b> 24 August 2020 20:47<br>
<b>To:</b> Daan van Gorkum <daan.vangorkum@vusam.com><br>
<b>Cc:</b> Dovecot Mailing List <dovecot@dovecot.org><br>
<b>Subject:</b> Re: Metric label values truncated when using OpenMetrics endpoint</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">On Sat, Aug 22, 2020 at 00:31:36 +0000, Daan van Gorkum wrote:<br>
> Hi,<br>
> <br>
> Recently we upgraded to Dovecot 2.3.11.3 and configured an example metric<br>
> like this:<br>
> <br>
> <br>
> metric imap_command {<br>
> event_name = imap_command_finished<br>
> group_by = cmd_name tagged_reply_state user remote_ip<br>
<br>
Grouping by remote_ip seems a bit dangerous unless the ips are somehow<br>
limited. Each unique value will result in (permanent) memory allocation, so<br>
this has the potential to slowly grow the stats process large enough that<br>
the vsize limit kicks in and the stats process gets killed and respawned.<br>
<br>
> }<br>
...<br>
> While the result is great, I noticed that some metrics are being truncated<br>
> (three dots at the end of the label value):<br>
> <br>
> dovecot_imap_command_duration_usecs_sum{cmd_name="FETCH",tagged_reply_state="OK",user="xxxxxxxxxxx.inbox@xxxxxxxxxxxxx…",remote_ip="XXXX:XXXX:XXXX:XXXX:cc6b:cc7a:d…"} 2346 1598055662473<br>
> <br>
> I couldn't find this information in the documentation so I'm wondering if<br>
> this is a bug.<br>
<br>
Hm. The submetric names are truncated to 32 bytes because nobody will ever<br>
want metrics bigger than that. ;) Obviously, we need to revisit that<br>
decision. There is no workaround that I can think of.<br>
<br>
Jeff.<br>
<br>
-- <br>
I'm somewhere between geek and normal.<br>
- Linus Torvalds<br>
</div>
</span></font></div>
</body>
</html>