[three]Bean

I wrote the code for it back in 2012, but it wasn't until today that I got Fedora Infrastructure's collectd instance tracking fedmsg messages:

We're tracking fedmsg messages in other places like datanommer, irc, and the identi.ca bot, but having them in collectd is cool because that's the place we go to monitor all our other system stats. All of our stuff in one place (but not all of our eggs in one basket).

You can click here to mess around with it.

fedmsg (the Fedora Infrastructure Message Bus) now has a full list of published message topics with example messages and more.

For instance, one of the topics on which the koji build system emits messages is org.fedoraproject.prod.buildsys.build.state.change. The docs there show:

• The topic.
• Some description of the event.
• An example message in JSON format. This is what you would see if you ran $ fedmsg-tail --really-pretty.
• Some description of what you would get if you passed the example message into some of the functions in the fedmsg.meta python module. This is the stuff you see in the #fedora-fedmsg irc channel and on the identi.ca bot.

Just in case you didn't know, you can listen to the public fedmsg bus (with no configuration) by running:

$ sudo yum install fedmsg
$ fedmsg-tail --really-pretty

If you want to program something that responds to fedmsg messages, check out the docs on consuming messages from python -- the new list of topics should come in handy.

Quick Timeline:

• February, 2012 - I started thinking about fedmsg.
• March, 2012 - Development gets under way.
• July, 2012 - Stuff gets working in staging.
• August-September, 2012 - The first messages hit production. We notice that some messages are getting dropped. We chalk it up to programming/configuration oversights. We are correct about that in some cases.
• October-November, 2012 - Some messages are still getting dropped. Theory develops that it is due to zeromq2's lack of TCP_KEEPALIVE. It takes time to package zeromq3 and test this, integrate it with Twisted bindings, and deploy. More message sources come online during this period. Other stuff like externally consuming messages [1] [2], datanommer [3] [4], and identica [5] happen too.
• January, 2013 - I enabled the TCP_KEEPALIVE bits in production at FUDCon Lawrence.

I haven't noticed any dropped messages since then: a marked improvement. However, our volume of messages is so much higher now that it is difficult to eyeball. If you notice dropped messages, please let me know in #fedora-apps on freenode.

Back in Rochester after a wild ride at FUDCon. Here's a rundown of my participation (deets):

• Gave a lightning talk on pkgwat and a session on fedmsg.
• Worked out an API design for datagrepper with Ian Weller.
• Figured out a mechanism for end users to validate incoming fedmsg messages talking with Luke Macken.
• Toshio and I brought pkgdb into the fedmsg brood.
• It's been a long time coming, but I updated fedmsg in our production environment to be using zeromq3's TCP_KEEPALIVE features. We'll see if this solves our message dropping problem.
• We moved a new release of the /packages webapp to production which includes my dogpile.cache work.
• Jordan Sissel remotely hooked fedmsg up to the logstash demo.
• Talked with Dennis Gilmore about hooking koji up to fedmsg. We have a plan and it shouldn't be too much longer. Getting messages out of koji was the #1 request I heard at FUDCon.
• Also talked with Dennis about getting fedmsg messages out from secondary arch composes (the rel-eng process) and with Seth Vidal about getting fedmsg messages out from copr and our private cloud. Both situations require bringing messages in from untrusted environments and so will require some new measures. Plan++.
• Lots of discussion about Fedora Badges (the stack for which needs a lot of love). I'll be buckling down more on it once I finish the current phase of fedmsg, but having the discussions out about infrastructure, goals, and scope with the whole group was a good thing.
• Some good bar-time discussion of the GNOME OPW and how to make it more effective!
• Met pingou, the French crew, and really everyone else. The Fedora community is full of some pretty awesome people. :)