Skip to content
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

Log connection info on start #18

Open
andrewvc opened this issue Feb 9, 2017 · 2 comments
Open

Log connection info on start #18

andrewvc opened this issue Feb 9, 2017 · 2 comments
Labels
blocked Issue blocked by one or more other issues bug Something isn't working plugin:input Issues affecting the Input Plugin

Comments

@andrewvc
Copy link
Contributor

andrewvc commented Feb 9, 2017

It'd be nice to log the info about which host we've connected to both before and after connect for auditability.

@merretbuurman
Copy link

merretbuurman commented Oct 17, 2018

Hi! I agree. In my logs, there is a line "Connected to RabbitMQ at", but then it is empty. The code to display this is clearly there, but not working properly.

logstash_1  | [2018-10-17T16:26:08,894][INFO ][org.logstash.beats.Server] Starting server on port: 5044
logstash_1  | [2018-10-17T16:26:11,967][INFO ][logstash.inputs.rabbitmq ] Connected to RabbitMQ at 
logstash_1  | [2018-10-17T16:26:13,090][INFO ][logstash.agent           ] Successfully started Logstash API endpoint {:port=>9600}

(I'm using Logstash 6.4.2 as a OSS docker image, btw... But I've seen this in my previous 6.x Logstash deployments too).

@yaauie yaauie transferred this issue from logstash-plugins/logstash-input-rabbitmq Nov 22, 2019
@yaauie
Copy link
Contributor

yaauie commented Nov 22, 2019

It looks like it's attempting to extract the :host property when logging, but the hash contains a :hosts (plural) instead.

I'm flagging this as blocked by #12 since it modifies the mapping to use :addresses.

I'll follow up on this once we figure out the path forward for the multiple host support.

@yaauie yaauie added blocked Issue blocked by one or more other issues bug Something isn't working plugin:input Issues affecting the Input Plugin labels Nov 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked Issue blocked by one or more other issues bug Something isn't working plugin:input Issues affecting the Input Plugin
Projects
None yet
Development

No branches or pull requests

3 participants