processone / processone/ejabberd

Get STUN/TURN usage statistics from ejabberdctl

Open
#3,441 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Component:TURN Kind:Feature
Dominant language
Erlang
Stars
6.7k
Forks
1.6k
PR merge metrics
No merged PRs in 30d

Description

Is your feature request related to a problem? Please describe.
At this time, there is no way to get stats or usage statistics from ejabberdctl about STUN/TURN features.

Describe the solution you'd like
It would be good (I think) that one could retrieve information similar to what one can retrieve with XMPP, on the use of STUN/TURN, with ejabberdctl commands, such as (but not limited to) total/average data relayed, average link duration, per user stats, etc

Describe alternatives you've considered
The only way to do something related is to change the log verbosity to 'info' and grep "Offering STUN/TURN" or "Relayed" to obtain some incomplete infos.

Additional context
I am co-administrator of the chapril.org XMPP server, which is open to the public, and we recently configured the server to support audio/video calls.

Thank you very much,
Regards

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the ejabberdctl command entry points and the existing STUN/TURN logging mentioned in the issue. Define which statistics are required, including relayed data, link duration, and per-user usage, and how the commands should expose them; the work is done when the agreed metrics can be retrieved without relying on log grepping.

Written by the indexing model from the issue text.

Assessment

Tech stack
erlang
Domain
networking, observability
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.