search for: auth_passdb_request_finish

Hi, Dovecot v2.3.11.3 (502c39af9) auth_passdb_request_finished appears to fire twice for an IMAP login using a Redis passdb. auth_request_finished only fires once. In the debug log below, the line "Finished passdb lookup" appears to be logged twice (once by "auth" and once by "auth-worker"). However, the actual passdb lookup...

Hi, Dovecot v2.3.11.3 (502c39af9) auth_passdb_request_finished appears to fire twice for an IMAP login using a Redis passdb. auth_request_finished only fires once. In the debug log below, the line "Finished passdb lookup" appears to be logged twice (once by "auth" and once by "auth-worker"). However, the actual passdb lookup...

...mpt status (successful or failed). My server uses a simple auth (with LDAP backend) and 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_userd...

Is there any additional documentation/information around the new stats module. Have added some metrics just to see what they produce ## ## Metrics ### metric imap { ??? event_name = imap_command_finished ??? #source_location = example.c:123 ??? #categories = ??? fields = name args running_usecs bytes_in bytes_out ??? #filter { ??? #??? field_key = wildcard ??? #} } metric sql { ???

..., but whatever I declare in metric, it always show 0. None of these auth_* requests exist in 2.3.6. > 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_clien...

...nMetrics 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 Gorkum <daan.vangorkum at vusam.com...

...akes 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 to have the remote_ip field as well a...

...akes 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 to have the remote_ip field as well a...

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