[OpenSIPS-Users] Getting call analytics to Elasticsearch

[Calvin Ellison]

Is there any best practice or standard method of getting data from OpenSIPS
to Elasticsearch?

The scenario is an internal call filter that will block or permit a call.
e.g. 503 route advance or 603 stop route. Checks are performed against
pre-populated caches and database queries, and we want the results of those
checks to ultimately reach Elasticsearch.

I'd prefer to avoid file-based things like syslog + logstash. The "OpenSIPS
and BigData" presentation from 2016 suggested using the Elasticsearch REST
API directly with async(rest_post()) or RabbitMQ. Our experience
with Elasticsearch indicates it will not keep up with our call volume
without a message queue, and now I'm seeing talking about Kafka being the
new standard for this.

Is this a solved problem?


Regards,

*Calvin Ellison*
Senior Voice Operations Engineer
calvin.ellison at voxox.com
+1 (213) 285-0555

-----------------------------------------------
*voxox.com <http://www.voxox.com/> *
5825 Oberlin Drive, Suite 5
San Diego, CA 92121
[image: Voxox]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20201125/9bf6e060/attachment-0001.html>