# Beats module for JMS queues

**URL:** <https://discuss.elastic.co/t/beats-module-for-jms-queues/374427>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [February 12, 2025, 12:43pm UTC](https://discuss.elastic.co/t/beats-module-for-jms-queues/374427 "2025-02-12T12:43:51Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![joaorr13](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joaorr13/32/141324_2.png) [@joaorr13](https://discuss.elastic.co/u/joaorr13)\
**Post date:** [February 12, 2025, 12:43pm UTC](https://discuss.elastic.co/t/beats-module-for-jms-queues/374427/1 "2025-02-12T12:43:51Z")

</div>

Hey,  
I want to send the logs collected by Filebeat to a Solace broker and then to Logstash. I know that there is no module for Solace and for JMS in general. In Logstash there is a JMS inetgration. My question would be, the only solution would be to have a seperate server that receives from beats and then publishes the data to Solace and then using the the JMS integration in Logstash subscribe?

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [February 12, 2025, 1:24pm UTC](https://discuss.elastic.co/t/beats-module-for-jms-queues/374427/2 "2025-02-12T13:24:27Z")

</div>

Hello,

Filebeat has limited outputs, it only support sending data to the following destinations:

- Elasticsearch Service (Elastic Cloud)
- Elasticsearch
- Logstash
- Kafka
- Redis

So, I don't think you can send data directly from Filebeat to this Solace broker, you need something in between like Logstash and see if Logstash has any output that would work in this Solace broker.

I'm not familiar with Solace, so I do not know how you can send data to it.

---

<div class="post-metadata">

**Author:** ![joaorr13](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joaorr13/32/141324_2.png) [@joaorr13](https://discuss.elastic.co/u/joaorr13)\
**Post date:** [February 12, 2025, 3:18pm UTC](https://discuss.elastic.co/t/beats-module-for-jms-queues/374427/4 "2025-02-12T15:18:49Z")

</div>

Do you think using Logstash would be a better solution than any other modules of this webpage:  
[Configure the output | Filebeat Reference [8.17] | Elastic](https://www.elastic.co/guide/en/beats/filebeat/current/configuring-output.html)

---

<div class="post-metadata">

**Author:** ![ahmed\_charafouddine](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ahmed_charafouddine/32/45129_2.png) [@ahmed\_charafouddine](https://discuss.elastic.co/u/ahmed_charafouddine)\
**Post date:** [February 13, 2025, 12:19pm UTC](https://discuss.elastic.co/t/beats-module-for-jms-queues/374427/5 "2025-02-13T12:19:26Z")

</div>

No, you don’t necessarily need a separate server since you can configure Logstash’s JMS integration to connect directly to a Solace broker once you’ve set up the required JMS client libraries. However, if your architecture demands additional processing, scaling, or separation of concerns, using an intermediary server to publish to Solace can be a viable approach.