[OpenSIPS-Users] dashboard stats from opensips

[nz deals]

Thank you, Brett.
My thoughts have been on events and Redis ;) I'll also explore RabbitMQ,
thanks for the suggestion. From what I gather, we can utilize
E_DLG_STATE_CHANGED within the event route. Could you guide me on how to
retrieve the dialogid/callid and its state? If I can access this
information in the event_route[E_DLG_STATE_CHANGED], storing the value
would be straightforward.

Thanks

On Thu, 4 Apr 2024 at 10:13, Brett Nemeroff <brett at nemeroff.com> wrote:

> I'd recommend using the events and rabbitmq. You should be able to do just
> about anything with that.
>
> What cps are you processing?
>
> On Wed, Apr 3, 2024 at 3:46 PM nz deals <nzdealshelp at gmail.com> wrote:
>
>> Thanks Ben,
>>
>> The issue with the scheduled task is that it introduces a delay. I'm
>> exploring methods to enable real-time display. By streaming events directly
>> from OpenSIPS, we could achieve live updates on the display.
>>
>>
>> Thank you
>>
>> Regards,
>> Jason
>>
>>
>> On Thu, 4 Apr 2024 at 06:15, Ben Newlin <Ben.Newlin at genesys.com> wrote:
>>
>>> OpenSIPS will already track some very basic statistics like this for you
>>> using the Statistics module.
>>>
>>>
>>>
>>> https://opensips.org/docs/modules/3.4.x/statistics.html
>>>
>>>
>>>
>>> For example, the Dialog module exposes concurrent calls.
>>>
>>>
>>>
>>> We have a scheduled job that queries those stats via MI and pushes them
>>> into our external metrics system, allowing us to create dashboards from the
>>> data.
>>>
>>>
>>>
>>> Ben Newlin
>>>
>>>
>>>
>>> *From: *Users <users-bounces at lists.opensips.org> on behalf of nz deals <
>>> nzdealshelp at gmail.com>
>>> *Date: *Wednesday, April 3, 2024 at 1:03 PM
>>> *To: *Bogdan-Andrei Iancu <bogdan at opensips.org>
>>> *Cc: *OpenSIPS users mailling list <users at lists.opensips.org>
>>> *Subject: *Re: [OpenSIPS-Users] dashboard stats from opensips
>>>
>>> * EXTERNAL EMAIL - Please use caution with links and attachments *
>>>
>>>
>>> ------------------------------
>>>
>>> Hi Bogdan,
>>>
>>>
>>>
>>> Yes, something along the lines of the OpenSIPs control panel, but I'm
>>> looking for very basic statistics, such as the details of currently active
>>> calls and a straightforward graph displaying concurrent calls.
>>>
>>>
>>> Thank you
>>>
>>>
>>>
>>> Regards,
>>>
>>> Jason
>>>
>>>
>>>
>>> On Thu, 4 Apr 2024 at 03:27, Bogdan-Andrei Iancu <bogdan at opensips.org>
>>> wrote:
>>>
>>> Hi Jason,
>>>
>>> Have you checked the Dashboard in OpenSIPS Control Panel ?
>>>
>>> Regards,
>>>
>>> Bogdan-Andrei Iancu
>>>
>>> OpenSIPS Founder and Developer
>>>    https://www.opensips-solutions.com
>>>    https://www.siphub.com
>>>
>>> On 03.04.2024 13:54, nz deals wrote:
>>> > Hi everyone,
>>> >
>>> > I'm seeking guidance on creating a dashboard. I'm considering saving
>>> > dialog events in Redis (straight from OpenSIPS), allowing my dashboard
>>> > to directly access the Redis cache. Do you think this is a wise
>>> > strategy, or do you have any alternative suggestions? Any expert's
>>> > suggestion will be highly appreciated. In fact if someone has any
>>> > example to check, raise dialog events like call, ringing, 183,
>>> > answered , cancel and bye etc...
>>> >
>>> > Thank you
>>> >
>>> > Regards,
>>> > Jason
>>> >
>>> > _______________________________________________
>>> > 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
>>
> _______________________________________________
> 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/20240404/08f1ed94/attachment.html>