It’s been a while since the last post, but I wanted to share this pearl in RESAM I came across today with regard to the dispatcher discovery process. There are three settings which dictate the agent’s behaviour, but it is more involved than just three switches. As there is only a pdf “instant report” available from the RES console I went down the rabbit hole again to create something more useful.

My solution for integrating an iPython notebook in Jekyll. It uses an iframe around an nbviewer page referring to a github gist.

The CSS to make the iframe resize nicely was stolen from Michael Lancaster and I add an inline style in the outer div tag to set the height. It would be nice to have that automatically, but as far as I can tell that’s not possible without some javascript voodoo I prefer to avoid.

I decided to move away from for reasons. Attracted to a static site generator, wanting some more flexibility and control, planning to build out my github repositories etc. signs were pointing towards Jekyll. I forked a theme I liked, started migrating some old blog posts, and after some modifications I felt it’s time to go ahead and make the initial commit.

Working on a little dashboard / status report for AM I wanted to include some information on the dispatchers. Most of it is straightforward stuff from the tblDispatchers table but I found another one of these RES peculiarities. Some of the settings for a dispatcher can be defined at a global level (Infrastructure -> Datastore -> Settings -> Global Settings) which can be overridden for a specific dispatcher (Dispatcher Properties -> Settings). So how can we include the effective setting straight from SQL?

To gain a better understanding of the communication protocol between agents and dispatchers we can use a couple of different tools. Ideally we capture the communication in bulk and store it in such a way that we can analyze it with a variety of different tools. Using command line tools and scripting will allow us to start and stop the capturing with relative ease so we can set up different usage scenarios and focus on specific interaction. Let’s get to work.