# Feature request: 'logstash-output-gelf' plugin TLS support

**URL:** <https://discuss.elastic.co/t/feature-request-logstash-output-gelf-plugin-tls-support/94092>\
**Category:** Logstash\
**Created:** [July 21, 2017, 9:55am UTC](https://discuss.elastic.co/t/feature-request-logstash-output-gelf-plugin-tls-support/94092 "2017-07-21T09:55:52Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bragolgirith](https://avatars.discourse-cdn.com/v4/letter/b/df705f/32.png) [@Bragolgirith](https://discuss.elastic.co/u/Bragolgirith)\
**Post date:** [July 21, 2017, 9:55am UTC](https://discuss.elastic.co/t/feature-request-logstash-output-gelf-plugin-tls-support/94092/1 "2017-07-21T09:55:52Z")

</div>

In Graylog it is possible to configure a GELF TCP Input with TLS, but from what I gather, the [logstash gelf output plugin](https://www.elastic.co/guide/en/logstash/current/plugins-outputs-gelf.html) doesn't currently support sending events over secured TCP.  
Sounds like something important to add to a future version 🙂

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [July 21, 2017, 11:39am UTC](https://discuss.elastic.co/t/feature-request-logstash-output-gelf-plugin-tls-support/94092/2 "2017-07-21T11:39:28Z")

</div>

This seems to be a community maintained plugin, so I would recommend creating an issue requesting this feature on the [GitHub repository.](https://github.com/logstash-plugins/logstash-output-gelf).

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 18, 2017, 11:39am UTC](https://discuss.elastic.co/t/feature-request-logstash-output-gelf-plugin-tls-support/94092/3 "2017-08-18T11:39:30Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
