-
Notifications
You must be signed in to change notification settings - Fork 295
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
WIP: AMQP support #1179
WIP: AMQP support #1179
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #1179 +/- ##
===========================================
- Coverage 75.11% 75.08% -0.04%
===========================================
Files 318 288 -30
Lines 14402 13267 -1135
Branches 1911 1793 -118
===========================================
- Hits 10818 9961 -857
+ Misses 3137 2909 -228
+ Partials 447 397 -50
|
There are speed problems and problems with unacked messages. Postponing this |
|
the heartbeat parameter for pika has been renamed
@wagner-certat what do you think about using "lazy queues" feature? I think is something that we miss a lot due a lot of messages that stuck on experts (like cymru-whois, gethostbyname and deduplicator). I think (not sure), we only need to pass the |
On this line (https://github.com/certtools/intelmq/blob/dev-amqp/intelmq/lib/pipeline.py#L39) it seems that we need to add Also, on this line (https://github.com/certtools/intelmq/blob/dev-amqp/intelmq/lib/pipeline.py#L41) it seems now we have three broker options, and I guess the one on line 41 will be required by intelmqctl |
Ad lazy queues: Thanks for the pointer, definitely
yes, thanks.
What do you mean? |
and fetch queue status from website
fa4224d
to
f905831
Compare
AMQP support is feature-complete, needs still to be tested on development machines and some unittests are needed.
intelmqctl