One of the blogs I follow regularly is Brent Ozar‘s. He does an excellent job pointing out or explaining issues that dba’s need to think about. This post from a few days ago is an excellent case in point. Having a server that sits in the same infrastructure and that you can let long running queries run on without issue is wonderful. No more worries about disconnections or battery failures stopping long running queries.

In Part 1, we covered how to get telegraf to execute a stored procedure on a schedule. This time we’ll take a look at what that procedure looks like. What is Influx Line Protocol format Telegraf is expecting the data to be returned in InfluxDB Line Protocol format. It’s a very simple text format that contains 4 parts. [measurement],[tags] [fields] [timestamp] Measurement This is the name of the metric in influx.

I love using telegraf and the sql server plugin that Tracy and Mark have championed. It’s an integral part of the Collecting Performance Metrics presentation that Tracy has given to about a billion people so far. It does have a few unfortunate limitations though since it doesn’t support SQL Server 2005. Which is sad because I still have a few instances which I cannot yet retire. So let’s fix that.