# Best way to "forward" logs to another system for additional routing/alerting

**URL:** <https://community.graylog.org/t/best-way-to-forward-logs-to-another-system-for-additional-routing-alerting/4665>\
**Category:** Graylog Central (peer support)\
**Created:** [March 21, 2018, 5:11pm UTC](https://community.graylog.org/t/best-way-to-forward-logs-to-another-system-for-additional-routing-alerting/4665 "2018-03-21T17:11:50Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![rayterrill](https://avatars.discourse-cdn.com/v4/letter/r/65b543/32.png) [@rayterrill](https://community.graylog.org/u/rayterrill)\
**Post date:** [March 21, 2018, 5:11pm UTC](https://community.graylog.org/t/best-way-to-forward-logs-to-another-system-for-additional-routing-alerting/4665/1 "2018-03-21T17:11:50Z")

</div>

The Graylog alerting mechanisms in the current release are not super flexible.

We’ve built an alert that sends messages from a stream to a HTTP callback which is running some NodeJS code for additional routing and alerting.

I was just wondering if there was a better way.

I looked at the Graylog Outputs, but there doesn’t appear to be a HTTP output or GELF HTTP output available in either core or the marketplace.

Is anyone else doing this and have a slicker approach that I’m not thinking of?

Cheers,  
-Ray

---

<div class="post-metadata">

**Author:** ![jochen](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jochen/32/8_2.png) [@jochen](https://community.graylog.org/u/jochen)\
**Post date:** [March 22, 2018, 8:16am UTC](https://community.graylog.org/t/best-way-to-forward-logs-to-another-system-for-additional-routing-alerting/4665/2 "2018-03-22T08:16:18Z")

</div>

> [@rayterrill](#):
>
> I looked at the Graylog Outputs, but there doesn’t appear to be a HTTP output or GELF HTTP output available in either core or the marketplace.

You can always write your own plugins for these.

---

<div class="post-metadata">

**Author:** ![rayterrill](https://avatars.discourse-cdn.com/v4/letter/r/65b543/32.png) [@rayterrill](https://community.graylog.org/u/rayterrill)\
**Post date:** [March 22, 2018, 2:05pm UTC](https://community.graylog.org/t/best-way-to-forward-logs-to-another-system-for-additional-routing-alerting/4665/3 "2018-03-22T14:05:46Z")

</div>

Right. But unfortunately my Java skills are nonexistent.

Would it be worth putting in a feature request for an HTTP Stream Output or maybe a HTTP GELF Output to be added to Core? I think that could be beneficial for a ton of people. It sort of already exists at the alert notification level and I’m using it there, just not at the Streams level.

---

<div class="post-metadata">

**Author:** ![jochen](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jochen/32/8_2.png) [@jochen](https://community.graylog.org/u/jochen)\
**Post date:** [March 22, 2018, 2:23pm UTC](https://community.graylog.org/t/best-way-to-forward-logs-to-another-system-for-additional-routing-alerting/4665/4 "2018-03-22T14:23:03Z")

</div>

> [@rayterrill](#):
>
> Would it be worth putting in a feature request for an HTTP Stream Output or maybe a HTTP GELF Output to be added to Core?

Please contact our sales team via [https://www.graylog.org/contact-sales](https://www.graylog.org/contact-sales) or [sales@graylog.com](mailto:sales@graylog.com) to discuss the possibility to sponsor a feature for one of the next Graylog versions.

---

<div class="post-metadata">

**Author:** ![rayterrill](https://avatars.discourse-cdn.com/v4/letter/r/65b543/32.png) [@rayterrill](https://community.graylog.org/u/rayterrill)\
**Post date:** [March 22, 2018, 2:32pm UTC](https://community.graylog.org/t/best-way-to-forward-logs-to-another-system-for-additional-routing-alerting/4665/5 "2018-03-22T14:32:42Z")

</div>

I’ll see what I can do with that internally. We’re government so that could be a little tricky. I may put a feature request in on github in the meantime as a placeholder. Thanks for all your help mate.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\
**Post date:** [April 5, 2018, 2:32pm UTC](https://community.graylog.org/t/best-way-to-forward-logs-to-another-system-for-additional-routing-alerting/4665/6 "2018-04-05T14:32:50Z")

</div>

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