New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GELF UDP not setting gl2_remote_ip? #3980

Closed
BenWoodford opened this Issue Jul 5, 2017 · 1 comment

Comments

Projects
None yet
3 participants
@BenWoodford

BenWoodford commented Jul 5, 2017

I'm using a GELF UDP input and not getting a gl2_remote_ip field set. I may just be doing this wrong, or haven't enabled an option, but I cannot find anything in the docs that references such an option.

Expected Behavior

gl2_remote_ip should be accessible via rules and "All Fields" on the Stream

Current Behavior

It's not.

Steps to Reproduce (for bugs)

  1. Run Graylog 2.23
  2. GELF UDP Input
  3. Send some messages
  4. Incoming messages don't have the IP set

Context

These are feeding directly from a desktop application (C#) on user computers, and I'd like to be able to GeoIP Map where it's all coming from.

Your Environment

Using the AMI for Graylog 2.2.3+7adc951 on graylog (Oracle Corporation 1.8.0_101 on Linux 3.13.0-119-generic)

  • Graylog Version: Graylog 2.2.3+7adc951 on graylog (Oracle Corporation 1.8.0_101 on Linux 3.13.0-119-generic)
  • Elasticsearch Version: Whatever comes with the AMI for the above version
  • MongoDB Version: See above
  • Operating System: See above
  • Browser version: Irrelevant, but Chrome 59.0.3071.115

@joschi joschi added the bug label Jul 5, 2017

@joschi joschi self-assigned this Jul 5, 2017

joschi added a commit that referenced this issue Jul 5, 2017

Keep remote address in NettyTransport with message aggregation
The `NettyTransport.MessageAggregationHandler#messageReceived()` method
failed to pass the original source address of the message to the following
handlers, so that any aggregating input (such as the GELF UDP input) lost
the information.

Fixes #3980

@wafflebot wafflebot bot added the in progress label Jul 5, 2017

@joschi

This comment has been minimized.

Contributor

joschi commented Jul 5, 2017

@BenWoodford Thanks for reporting this issue. I could reproduce it and a fix will be included in one of the next versions of Graylog.

@bernd bernd added the triaged label Jul 10, 2017

@wafflebot wafflebot bot removed the in progress label Jul 10, 2017

dennisoelkers added a commit that referenced this issue Jul 10, 2017

Keep remote address in NettyTransport with message aggregation (#3982)
The `NettyTransport.MessageAggregationHandler#messageReceived()` method
failed to pass the original source address of the message to the following
handlers, so that any aggregating input (such as the GELF UDP input) lost
the information.

Fixes #3980

joschi added a commit that referenced this issue Jul 11, 2017

Keep remote address in NettyTransport with message aggregation (#3982)
The `NettyTransport.MessageAggregationHandler#messageReceived()` method
failed to pass the original source address of the message to the following
handlers, so that any aggregating input (such as the GELF UDP input) lost
the information.

Fixes #3980

(cherry picked from commit 35cea15)

kroepke added a commit that referenced this issue Jul 11, 2017

Keep remote address in NettyTransport with message aggregation (#3982) (
#3988)

The `NettyTransport.MessageAggregationHandler#messageReceived()` method
failed to pass the original source address of the message to the following
handlers, so that any aggregating input (such as the GELF UDP input) lost
the information.

Fixes #3980

(cherry picked from commit 35cea15)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment