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 amqp input keepalive #1010

Closed
ynfiesta opened this Issue Mar 1, 2015 · 8 comments

Comments

Projects
None yet
5 participants
@ynfiesta

ynfiesta commented Mar 1, 2015

when hosting graylog and rabbitmq in azure, azure kills the gelf amqp input connection if it is inactive for a minute.
This could be solved by adding a keepalive setting to the gelf amqp input.
In the meantime I am sending and empty message "{}" every 40 seconds to keep the connection alive

@joschi joschi added the inputs label Mar 2, 2015

@bernd bernd assigned bernd and unassigned bernd Mar 2, 2015

@bernd bernd added this to the 1.1.0 milestone Mar 2, 2015

@bernd

This comment has been minimized.

Member

bernd commented Mar 2, 2015

Thanks for the report. We will expose the heartbeat timeout in the input configuration.

Might also be related to #699

@kroepke kroepke self-assigned this May 26, 2015

kroepke added a commit that referenced this issue May 26, 2015

kroepke added a commit that referenced this issue May 26, 2015

kroepke added a commit that referenced this issue May 26, 2015

@kroepke kroepke closed this in c7c28a6 May 27, 2015

@zolech

This comment has been minimized.

zolech commented Jun 23, 2015

Hello,

I don't see this option in 1.1.3 while creating input. After upgrading from 1.0.2 all my AMQP inputs stopped working with message "Mandatory configuration field heartbeat is missing" but I cannot set it because there is no "Heartbeat timeout" field on input creation page :<

@bernd

This comment has been minimized.

Member

bernd commented Jun 23, 2015

@zolech I will try to reproduce this.

@bernd

This comment has been minimized.

Member

bernd commented Jun 24, 2015

@zolech I was able to reproduce the problem with the "Mandatory configuration field heartbeat is missing" message after updating from 1.0 to 1.1. We will probably change this to not being mandatory in the future.

I cannot reproduce the problem that you do not see the "Heartbeat timeout" field when updating/creating an AMQP input. If you scroll down, you should be able to see it.
4p8aaaaaelftksuqmcc

bernd added a commit that referenced this issue Jun 24, 2015

Make heartbeat timeout option for AmqpTransport optional.
There is no reason to make this mandatory because there is a default.

Refs #1010 (comment about updating from 1.0 to 1.1)
@zolech

This comment has been minimized.

zolech commented Jun 24, 2015

Look, I am not joking. No heartbeat option on my screen. Version 1.1.3 (both server and web)

screenshot from 2015-06-24 09-12-15

@bernd

This comment has been minimized.

Member

bernd commented Jun 24, 2015

That is strange, I will investigate. Thanks for the feedback!

@zolech

This comment has been minimized.

zolech commented Jun 24, 2015

I got it working! It seems that one of my nodes hasn't been restarted during upgrade so it was still in 1.0.2. After restarting it came up as 1.1.3 and heartbeat options finally appeared. Sorry for bothering!

@bernd

This comment has been minimized.

Member

bernd commented Jun 24, 2015

@zolech Cool, glad it's working now! 😃

bernd added a commit that referenced this issue Jun 24, 2015

Make heartbeat timeout option for AmqpTransport optional.
There is no reason to make this mandatory because there is a default.

Refs #1010 (comment about updating from 1.0 to 1.1)

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