I want to analyze the customers who are consuming the data from the topic exchange.
Is there a way to get the history of binding to this topic exchange in the last 30 days or max available time limit?
Suppose since last 1 week 20 services consumed from the topic.
Then I can get these 20 services from binding history.
Thanks
No, RabbitMQ does not support this feature out of the box, but you may be able to implement this yourself using the Event Exchange:
https://www.rabbitmq.com/event-exchange.html
NOTE: the RabbitMQ team monitors the rabbitmq-users mailing list and only sometimes answers questions on StackOverflow.
Related
I would like to generate some statistics on massage traffic on one exchange based on header information, mainly routing key but ideally also other headers. Due to the large bandwidth involved I would like to not actually transmit the payload but only look at the header. I am looking at continuous traffic rates, not snapshot queue states.
Is this something that could be done with a specific configuration and an external program or would one have to approach this as a RabbitMQ plugin?
This would be best approached as a plugin. Please feel free to use the rabbitmq-users mailing list for assistance. I and other RabbitMQ core engineers monitor the list and help out.
NOTE: the RabbitMQ team monitors the rabbitmq-users mailing list and only sometimes answers questions on StackOverflow.
I need a queue with limited message inside considering not only message in queue but also the unacked ones. Is there a way to configure this server side? If yes is it possible using kobu as library?
Thank you
The RabbitMQ team monitors the rabbitmq-users mailing list and only sometimes answers questions on StackOverflow.
The documentation clearly states that queue length uses the count of ready messages: https://www.rabbitmq.com/maxlength.html
How do RabbitMQ taks perform one after another Not all the same time,
e.g.
We have 10 task that follow each other.
Task 1 end do task 2 etc..
The RabbitMQ team monitors the rabbitmq-users mailing list and only sometimes answers questions on StackOverflow.
Set your channel's prefetch (QoS) value to 1. Then, when you consume messages, RabbitMQ will only send one message and will not send more until that one message is acknowledged.
I suggest that you do all of the RabbitMQ tutorials, especially this one.
I need to use rabbitmq for a client requirement. Client suggested rabbit mq.
Based on some googling it looks like rabbitmq does not support replay of past messages from arbitary offsets unlike say kafka.
I just need a confirmation on whether this limitation is still valid. Any official url will be helpful.
Thanks.
R
The RabbitMQ team monitors the rabbitmq-users mailing list and only sometimes answers questions on StackOverflow.
Based on some googling it looks like rabbitmq does not support replay
of past messages
That's correct. Once a message is delivered and acknowledged (if the queue requires an ack) it is never available again and no trace of it remains in RabbitMQ.
I have been reading about Google Cloud Pub/Sub on their website, and it looks like a messaging solution that I have implemented, but I would consider moving to it so that my team does not have to maintain that code base. One detail that I have not seen the answer to, so far, is regarding the durability of subscriptions, topics, etc, after service restarts. I have probably missed it, and I am sure that this question must be answered somewhere, but if someone could point me to that information, I would be grateful. Thanks in advance!
From the Google Cloud Pub/Sub FAQ:
Are messages durable or persistent if the subscriber is not present?
Yes. The Pub/Sub system guarantees that subscriptions retain
unacknowledged messages in persistent storage for 7 days from the
moment they were published. In addition, note that subscriptions whose
client presence has not been detected for 30 days may be automatically
deleted. For example, if messages are pulled within 30 days of the
last Pull operation, this has the effect of restarting the 30 day
clock for the subscription deletion; however, any messages published
before 7 days may be lost regardless of their acknowledgment state.
UPDATE:
Now you can go to this page, in the Subscription section:
Thanks to #dxps for the update!