[kamailio] kamailio doesn't provide number of registered users stat when usrloc in db_mode=3 (#113)
19 Mar
2015
19 Mar
'15
5:38 p.m.
Running latest 4.2 with usrloc in db_mode=3. It seems "kamctl stats usrloc" or
"kamctl ul show" always shows 0 registered users even when there are registered
users (location table has entries).
This looks like a bug?
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/113
19 Mar
19 Mar
5:55 p.m.
It is not a bug. From the docs:
3.20. db_mode (integer)
...
3 - DB-Only scheme. No memory cache is kept, all operations being directly
performed with the database...
<snip>
...The lack of memory caching also disable the statistics exports.
On 19 Mar 2015 15:38, "mading087" <notifications(a)github.com> wrote:
Running latest 4.2 with usrloc in db_mode=3. It seems
"kamctl stats
usrloc" or "kamctl ul show" always shows 0 registered users even when
there
are registered users (location table has entries).
This looks like a bug?
—
Reply to this email directly or view it on GitHub
<https://github.com/kamailio/kamailio/issues/113>.
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
--
www.sipcentric.com
Follow us on twitter @sipcentric <http://twitter.com/sipcentric>
Sipcentric Ltd. Company registered in England & Wales no. 7365592. Registered
office: Faraday Wharf, Innovation Birmingham Campus, Holt Street,
Birmingham Science Park, Birmingham B7 4BB.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/113#issuecomment-83641974
24 Mar
24 Mar
6:19 p.m.
Charles Chance writes:
It is not a bug. From the docs:
3.20. db_mode (integer)
...
3 - DB-Only scheme. No memory cache is kept, all operations being directly
performed with the database...
<snip>
...The lack of memory caching also disable the statistics exports.
i would just like to add that there exists ul.db_users and
ul.db_contacts rpc commands that provide similar info than users and
contacts statistics.
-- juha
19 Mar
19 Mar
6:11 p.m.
Thanks for the info. The same text is in the 4.2 usrloc doc as well.
Stats are important in some business cases. Guess we can consider this an enhancement.
Wonder what is the best way to maintain the stats in db only mode.
1. change snmpstats to read from db instead of memory
2. maybe something easier than snmp, like acc/cdr from db?
Just look for some recommendations. Thanks,
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/113#issuecomment-83645924
6:15 p.m.
On 19 Mar 2015, at 17:10, mading087 <notifications(a)github.com> wrote:
Thanks for the info. The same text is in the 4.2
usrloc doc as well.
Stats are important in some business cases. Guess we can consider this an enhancement.
Wonder what is the best way to maintain the stats in db only mode.
1. change snmpstats to read from db instead of memory
That would not be smart - the number of hits on the database would not be low. I
don't
see this as a snmpstats function - could be a usrloc function.
2. maybe something easier than snmp, like acc/cdr from
db?
Counters are cool. Adding counters that keep track is propably the best way
forward.
But that will be confusing if you are using db-only mode with multiple servers, since
there are additions done somewhere else.
In the end if you want to check this with snmp I suggest you write your own scripts and
add to the MIB using the custom options in snmpd.conf - its' quite easy and would
solve
your problem.
As an alternative you can define your own script counter and have a background script
that runs your SQL query every X minutes and updates a counter that you can watch
with kamcmd and the old kamctl.
/O
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/113#issuecomment-83647063
6:20 p.m.
mading087 writes:
Thanks for the info. The same text is in the 4.2
usrloc doc as well.
Stats are important in some business cases. Guess we can consider this
an enhancement. Wonder what is the best way to maintain the stats in
db only mode.
1. change snmpstats to read from db instead of memory
2. maybe something easier than snmp, like acc/cdr from db?
Just look for some recommendations. Thanks,
it would, of course, be possible to implement the stat exports for
db_mode=3 too. just execute in the module a suitable db query.
-- juha
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/113#issuecomment-83649016
6:22 p.m.
Olle E. Johansson writes:
As an alternative you can define your own script
counter and have a
background script
that runs your SQL query every X minutes and updates a counter that
you can watch
with kamcmd and the old kamctl.
why would you need to run the query every X minutes instead of on demand
when the relevant kamctl command is given?
-- juha
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/113#issuecomment-83650025
8:06 p.m.
New subject: [kamailio] kamailio doesn't provide number of registered users stat when usrloc in db_mode=3 (#113)
On 19 Mar 2015, at 17:22, juha-h <notifications(a)github.com> wrote:
Olle E. Johansson writes:
If one for some reason wants the counter available at all times in Kamailio...
But I agree with you that it's not a good solution at all. Just brainstorming.
/O
As an alternative you can define your own script
counter and have a
background script
that runs your SQL query every X minutes and updates a counter that
you can watch
with kamcmd and the old kamctl.
why would you need to run the query every X minutes instead of on demand
when the relevant kamctl command is given?
6:40 p.m.
The script option with snmpd.conf seems ideal for my need. Thanks a lot for pointing that
out.
Think I'll give it try using python snmp-passpersist module.
Guess X minutes cron job would be easier for straight snmp calls like get, walk etc.
And the same python script can be hooked up with kamctl for on demand query as well.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/113#issuecomment-83654563
7:38 p.m.
mading087 writes:
Guess X minutes cron job would be easier for straight
snmp calls like
get, walk etc.
And the same python script can be hooked up with kamctl for on demand
query as well.
i don't like the idea of kamctl being dependent on python. best would
be adding sql queries to the module code. then the starts could be
fetched also via xmlrpc, etc.
-- juha
1 Apr
1 Apr
3:52 p.m.
I don't think it worth adding C code for external SQL query needs. IIRC, during early
SER times there was a command to execute any sql query via mi/fifo, but wasn't
feasible and easy to maintain, therefore removed.
I kamctl can be added using db cli application (e.g., mysql) with a bit of grep/sed/awk
will print only the value.
Fetching the value via xmlrpc should be possible via a bit of config scripting, inside
route[XMLRPC] intercept the command before dispatch_rpc() (search over the body or using
xmlops), do appropriate sql_query(...) via sqlops and push back a reply with a body in
xmlrpc format.
I would propose to close this item here.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/113#issuecomment-88467639
21 May
21 May
11:34 p.m.
Closed #113.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/113#event-311065272
3474
days inactive
3537
days old
11 comments
8 participants
participants (8)
-
Charles Chance -
Daniel-Constantin Mierla
-
Juha Heinanen -
juha-h
-
mading087
-
Olle E. Johansson
-
Olle E. Johansson -
Victor Seva