[OpenSIPS-Users] scheduled concurrent call reporting

[Khalil Khamlichi]

snmpstat data seems a little cryptic and difficult to parse, it might be
just me, so please tell me about your experience using snmpstat and how
easy was it for you to make it useful for your business case ?

On Wed, Jan 25, 2017 at 9:08 PM, Abdul Basit <basit.engg at gmail.com> wrote:

> Khalil,
>
> Why don't you consider snmpstat module for stats collection from opensips?
>
>
> On 25 Jan 2017 17:12, "Khalil Khamlichi" <khamlichi.khalil at gmail.com>
> wrote:
>
>> Liviu, you just saved my day. my plan is to push information to redis
>> every 10s maybe 5s if need there is, when dashboard is complete I might
>> consider saving the stream of data for plotting and further analysis.
>>
>>
>> On Wed, Jan 25, 2017 at 11:45 AM, Liviu Chircu <liviu at opensips.org>
>> wrote:
>>
>>> I do not see any problems with calling "get_profile_size()" from timer
>>> routes, event routes, etc. As such, you can safely bypass the block
>>> restriction using the following example:
>>>
>>> route [get_prof_sz_inboundCalls] {
>>>     get_profile_size("inboundCalls",,"$var(size)");
>>> }
>>>
>>> route [get_prof_sz_outboundCalls] {
>>>     get_profile_size("outboundCalls",,"$var(size)");
>>> }
>>>
>>> timer_route [mytimer, 1]
>>> {
>>>     route(get_prof_sz_inboundCalls);
>>>     xlog("inboundCalls: $var(size)\n");
>>>
>>>     route(get_prof_sz_outboundCalls);
>>>     xlog("outboundCalls: $var(size)\n");
>>> }
>>>
>>> Regards,
>>>
>>> Liviu Chircu
>>> OpenSIPS Developerhttp://www.opensips-solutions.com
>>>
>>> On 24.01.2017 01:05, Khalil Khamlichi wrote:
>>>
>>> the idea is that I don't need to get the number of calls 30 times per
>>> second which would happens if I save to redis on each invite. scheduling
>>> the saving to redis every 10 seconds serves  well my purpose but the
>>> timer_route doesn't seem to accept get_profile_size()
>>>
>>> any hints would be appreciated.
>>>
>>> On Mon, Jan 23, 2017 at 10:39 PM, Khalil Khamlichi <
>>> <khamlichi.khalil at gmail.com>khamlichi.khalil at gmail.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> I am trying to get call load information out of opensips at regular
>>>> intervals to get some sort of realtime view of the load on the server.
>>>>
>>>> After applying profiles on the the INVITEs, I have tried to call
>>>> get_profile_size from a timer_route.
>>>> I am getting error :
>>>>
>>>> CRITICAL:core:yyerror: parse error in config file
>>>> /usr/local//etc/opensips/opensips.cfg, line 483, column 38-39: Command
>>>> cannot be used in the block
>>>>
>>>> Any alternative solutions ?
>>>>
>>>> Thanks in advance.
>>>>
>>>> kkh
>>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20170126/081739f7/attachment.html>