Introducing Omnibug

Omnibug is a tool for web developers.  I wrote it because debugging an Omniture implementation is… painful.

The idea is that web metrics (or webanalytics, if you’re so inclined) systems generally make an HTTP request (usually an image) in order to pass along tracking information.  The URLs contain lots of parameters, conveniently URL-encoded so you can’t read them easily.

Omnibug is an extension to Firebug (without a doubt the best Firefox add-on available, driving a revolution in web UI development).  It adds a new panel with the decoded output of each such HTTP request, making it a breeze to see exactly what values were sent.

Though it was designed with Omniture in mind, it will work with other systems (also tested with Moniforce).  The patterns it looks for are fully configurable, so in theory it should work with any similar system.

An additional feature is the ability to log matching requests to the local filesystem.  While this feature was intended to support automated testing of metrics implementations, it may have other uses.

See the Omnibug page for downloads and full documentation.

Advertisements

2 thoughts on “Introducing Omnibug

  1. Joris

    Hi,

    Thank you very much for Omnibug! I’ve found in invaluable, and much easier to use that Adobe’s Digital Pulse bookmarklet.

    I’d love to see a post on automated testing of metrics implementations. Currently I’m using Selenium, with a lot of verifyEvals like: this.browserbot.getUserWindow().s.channel=mobile , or this.getEval(/[0-9*]-[0-9*]/.test(window.s.prop22))==true, but it’s very fiddly to maintain.

    Any suggestions?

    Like

    Reply
    1. simpsora Post author

      Hi Joris,

      Thanks! I’m glad you find Omnibug useful.

      In the past, some people have implemented automated testing by using the log to file method in Omnibug, executing their test suite, then verifying that the correct events occur in the log file. Unfortunately, the only really useful thing saved to the log file at this point is the unparsed request URL, so the verification requires parsing out the details of each URL. I’m open to any suggestions on how this could be made easier. Automating testing of metrics implementations would be a huge win for a lot of developers. Feel free to make suggestions, and stay tuned!

      Ross

      Like

      Reply

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s