Beanstalkd is a simple, fast work queueing daemon. Its interface is generic, but was originally designed for reducing the latency of page views in high-volume web applications by running time-consuming tasks asynchronously. A queue is something that lets you store "jobs" in it and later retrieve them. And some of the key attributes of a queue are the ability to easily store and retrieve items, the ability to never lose a job, and the ability to access the queue from several different languages.
Why use a Telegraf plugin for Beanstalkd?
Beanstalkd measures metrics about the number of requests your application is receiving, as well as the status codes of the responses. Monitoring the total number of requests can help you pinpoint surges in traffic, while monitoring 5xx and 4xx responses is good error detection. The Beanstalkd Telegraf plugin gathers these metrics for ingest into InfluxDB where you can monitor your application and create alerts that trigger when thresholds are exceeded.
How to monitor Beanstalkd queues using the Telegraf plugin
Setting up the Beanstalkd Telegraf Plugin requires that you enter the server information and optionally, the list of tubes to gather stats about. Once this is configured, the Beanstalkd Telegraf plugin will start sending metrics to your InfluxDB instance.
Key Beanstalkd metrics to use for monitoring
Some of the important Beanstalkd metrics that you should proactively monitor include:
Statistical information about the system as a whole
Statistical information about the specified tube