Mercurial > prosody-modules
view mod_http_user_count/mod_http_user_count.lua @ 5787:e79f9dec35c0
mod_c2s_conn_throttle: Reduce log level from error->info
Our general policy is that "error" should never be triggerable by remote
entities, and that it is always about something that requires admin
intervention. This satisfies neither condition.
The "warn" level can be used for unexpected events/behaviour triggered by
remote entities, and this could qualify. However I don't think failed auth
attempts are unexpected enough.
I selected "info" because it is what is also used for other notable session
lifecycle events.
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Thu, 07 Dec 2023 15:46:50 +0000 |
parents | a45f2f79e99b |
children |
line wrap: on
line source
local it = require "util.iterators"; local jid_split = require "util.jid".prepped_split; module:depends("http"); local function check_muc(jid) local room_name, host = jid_split(jid); if not hosts[host] then return nil, "No such host: "..host; elseif not hosts[host].modules.muc then return nil, "Host '"..host.."' is not a MUC service"; end return room_name, host; end module:provides("http", { route = { ["GET /sessions"] = function () return tostring(it.count(it.keys(prosody.full_sessions))); end; ["GET /users"] = function () return tostring(it.count(it.keys(prosody.bare_sessions))); end; ["GET /host"] = function () return tostring(it.count(it.keys(prosody.hosts[module.host].sessions))); end; ["GET /room/*"] = function (request, room_jid) local name, host = check_muc(room_jid); if not name then return "0"; end local room = prosody.hosts[host].modules.muc.rooms[name.."@"..host]; if not room then return "0"; end return tostring(it.count(it.keys(room._occupants))); end; }; });