Displaying 6 results from an estimated 6 matches for "auth_userdb_request_finish".
Did you mean:
auth_userdb_request_finished
2019 Jul 11
2
Getting login stats
...d supports only "auth_mechanisms = plain login"
I tried using the following metrics:
--------------------------------
metric auth_request_finished {
event_name = auth_request_finished
}
metric auth_passdb_request_finished {
event_name = auth_passdb_request_finished
}
metric auth_userdb_request_finished {
event_name = auth_userdb_request_finished
}
metric auth_client_request_started {
event_name = auth_client_request_started
}
metric auth_client_userdb_lookup_started {
event_name = auth_client_userdb_lookup_started
}
metric auth_client_passdb_lookup_started {
event_name = auth_clien...
2019 Jul 11
0
Getting login stats
...I tried using the following metrics:
>
>
> --------------------------------
> metric auth_request_finished {
> event_name = auth_request_finished
> }
>
> metric auth_passdb_request_finished {
> event_name = auth_passdb_request_finished
> }
>
> metric auth_userdb_request_finished {
> event_name = auth_userdb_request_finished
> }
>
> metric auth_client_request_started {
> event_name = auth_client_request_started
> }
>
> metric auth_client_userdb_lookup_started {
> event_name = auth_client_userdb_lookup_started
> }
>
> metric...
2020 Aug 25
2
Metric label values truncated when using OpenMetrics endpoint
...hat based on the logs but the OpenMetrics endpoint seem a lot easier.
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.
Thanks again!
Daan
________________________________
From: Josef 'Jeff' Sipek <jeff.sipek at open-xchange.com>
Sent: 24 August 2020 20:47
To: Daan van Gorku...
2020 Aug 26
0
Metric label values truncated when using OpenMetrics endpoint
...egating based on a subnet definitely makes sense.
> 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.
I haven't played with these events, but at least based on the docs [1],
auth_client_userdb_lookup_finished and auth_client_passdb_lookup_finished
events seem...
2020 Aug 27
1
Metric label values truncated when using OpenMetrics endpoint
...egating based on a subnet definitely makes sense.
> 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.
I haven't played with these events, but at least based on the docs [1],
auth_client_userdb_lookup_finished and auth_client_passdb_lookup_finished
events seem...
2020 Aug 22
2
Metric label values truncated when using OpenMetrics endpoint
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 {
port = 5000
}
}
While the result is great, I noticed that some metrics are being truncated