Hi!
I just committed a patch to snmpstats that use config framework variables to check if websockets and outbound is enabled. This opens up for a whole new set of SNMP data that exist in the config framework.
To summarize my findings:
- Config variables is a good way to expose configuration data - readonly or modifyable - between modules.
Adding readonly variables managed by your module like "enabled" or "db_connection_failed" helps.
- Counters/statistic variables (ser/kamailio names on the same thing) are really good to expose usage
of a module or a core feature
My conclusion is that more modules should expose config framework settings and counters. This not
only helps snmpstats, but also enables a lot of functionality through rpc and mi interfaces.
RPC and SNMP are cool. Using them, you can build a manageable Kamailio configuration.
We still have modules that expose functionality only using the old MI interface. Hopefully we
can work together to migrate more modules towards the RPC interface, add counters where
possible as well as configuration framework data.
On my wish list is dispatcher status - the ability to publish dispatcher node states and send alarms
when nodes fail. :-)
/O
Hi!
I'm trying to expose enabled transports to the SNMPstats management platform.
How do I discover if websockets/TLS (wss) and STCP/TLS is used?
I can guess that if the websocket, tls and xhttp modules are loaded we are ready to rock with wss - but that's just a guess.
Does the module itself know that it has TLS support or is that hidden deep down in the core?
/O