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

AMQP consumer stopped if message is empty #5170

Closed
hardiksondagar opened this issue Dec 20, 2018 · 0 comments · Fixed by #5176
Closed

AMQP consumer stopped if message is empty #5170

hardiksondagar opened this issue Dec 20, 2018 · 0 comments · Fixed by #5176
Labels
area/rabbitmq bug unexpected problem or unintended behavior
Milestone

Comments

@hardiksondagar
Copy link

Relevant telegraf.conf:

# Configuration for sending metrics to InfluxDB
[[outputs.influxdb]]
  urls = ["http://influx.domain.com:8086"]
  database = "sense"

# AMQP consumer plugin
[[inputs.amqp_consumer]]
  brokers = ["amqp://queue.domain.com:5672"]
  username = "RABBIT"
  password = "SECRET"
  exchange = "influx"
  queue = "influx"
  queue_durability = "durable"
  binding_key = ""
  prefetch_count = 500
  data_format = "influx"

System info:

OS

Linux version 4.15.0-1021-aws (buildd@lcy01-amd64-001) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #21-Ubuntu SMP Tue Aug 28 10:23:07 UTC 2018

Telegraf

Telegraf 1.9.0 (git: HEAD 2bf21c0d)

Steps to reproduce:

  1. Push blank/empty message to queue

Expected behavior:

Blank message should have dropped

Actual behavior:

It stopped consuming from the queue and connection stays idle in rabbitmq

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/rabbitmq bug unexpected problem or unintended behavior
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants