[asterisk-bugs] [JIRA] (ASTERISK-30147) Initial REDIS support for Device State changes

Alec Davis (JIRA) noreply at issues.asterisk.org
Thu Jul 21 18:41:09 CDT 2022


     [ https://issues.asterisk.org/jira/browse/ASTERISK-30147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alec Davis updated ASTERISK-30147:
----------------------------------

    Description: 
Creating an issue for gerrit to refer to.

We had a requirement to monitor device state, the requirement was that REDIS be the backend.

It could and was initially done with ARI but if that websocket stopped we were none the wiser.

In 2017 there was an asterisk-dev discussion " Adding a Key/Value Store mechanism to Asterisk" refer to :http://lists.digium.com/pipermail/asterisk-dev/2017-December/076721.html

Modeled from res_statsd and res_chan_stats we have a minimal implementation res_redisd and res_redis_device_state.


  was:
Creating an issue for gerrit to refer to.

We had a requirement to monitor device state, the requirement was that REDIS be the backend.

It could and was initially down with ARI but if that websocket stopped we were none the wiser.

In 2017 there was an asterisk-dev discussion " Adding a Key/Value Store mechanism to Asterisk" refer to :http://lists.digium.com/pipermail/asterisk-dev/2017-December/076721.html

Modeled from res_statsd and res_chan_stats we have a minimal implementation res_redisd and res_redis_device_state.



> Initial REDIS support for Device State changes
> ----------------------------------------------
>
>                 Key: ASTERISK-30147
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30147
>             Project: Asterisk
>          Issue Type: New Feature
>      Security Level: None
>          Components: Resources/NewFeature
>    Affects Versions: 19.5.0
>            Reporter: Alec Davis
>            Assignee: Alec Davis
>            Severity: Trivial
>
> Creating an issue for gerrit to refer to.
> We had a requirement to monitor device state, the requirement was that REDIS be the backend.
> It could and was initially done with ARI but if that websocket stopped we were none the wiser.
> In 2017 there was an asterisk-dev discussion " Adding a Key/Value Store mechanism to Asterisk" refer to :http://lists.digium.com/pipermail/asterisk-dev/2017-December/076721.html
> Modeled from res_statsd and res_chan_stats we have a minimal implementation res_redisd and res_redis_device_state.



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list