a12n left a comment (kamailio/kamailio#4389)
> Just out of curiousity, which modules (class) would be the user of this new
> API?
I've been experimenting with extending the `dispatcher` module to report
destination-related statistics as Prometheus metrics. Something like this:
```
kamailio_dispatcher_errors_total{group="1", dest="sip:127.0.0.1:5074",
status="503"} 1 1757450204729
kamailio_dispatcher_errors_total{group="1", dest="sip:127.0.0.1:5073",
status="503"} 1 1757450204729
kamailio_dispatcher_errors_total{group="1", dest="sip:127.0.0.1:5072",
status="503"} 1 1757450204729
```
And changes in this PR are a byproduct of those experiments.
I'm not sure if the `dispatcher` work is something viable (especially taking
into account potential performance problems with `xhttp_prom` you've described
in an issue earlier), but these changes seemed useful enough to be included.
Initially, I expected to find an exported API in `xhttp_prom` in some `struct`,
similar to what other modules do (e.g., `registrar_api_t` or `tm_api_t`).
However, it wasn't the case.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4389#issuecomment-3274432289
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/4389/[email protected]>_______________________________________________
Kamailio - Development Mailing List -- [email protected]
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the
sender!
