Monitor PostgreSQL With Telegraf and MetricFire

How to Monitor PostgreSQL With Telegraf and MetricFire

Table of Contents

Introduction

Monitoring the performance of your PostgreSQL databases is critical to ensuring they operate efficiently and support your applications without lag or downtime. It helps identify slow queries, resource bottlenecks, and potential database schema issues that could degrade performance over time. Proactive monitoring also ensures the database can scale effectively with your application’s needs, enhancing overall reliability and user satisfaction.

In this article, we'll detail how to use the Telegraf agent to collect PostgreSQL performance data that you can forward to a data source of your choice.

        

Getting Started with the Telegraf Agent

Telegraf is a plugin-driven server agent built on InfluxDB that collects and sends metrics/events from databases, systems, processes, devices, and applications. It is written in Go, compiles into a single binary with no external dependencies, and requires a minimal memory footprint. Telegraf is compatible with many operating systems and has many helpful output plugins and input plugins for collecting and forwarding a wide variety of system performance metrics. 

Install Telegraf (Linux/Redhat)

Download Telegraf and unzip it (see the Telegraf docs for up-to-date versions and installation commands for many operating systems). Packages and files are generally installed at /etc/telegraf/


Ubuntu/Debian
wget https://dl.influxdata.com/telegraf/releases/telegraf_1.30.0-1_amd64.deb
sudo dpkg -i telegraf_1.30.0-1_amd64.deb

RedHat/CentOS

wget https://dl.influxdata.com/telegraf/releases/telegraf-1.30.0-1.x86_64.rpm
sudo yum localinstall telegraf-1.30.0-1.x86_64.rpm

Configure an Output

You can configure Telegraf to output to various sources, such as Kafka, Graphite, InfluxDB, Prometheus, SQL, NoSQL, and more.

In this example, we will configure telegraf with a Graphite output. If you're not currently hosting your data source, start a 14-day free trial with Hosted Graphite by MetricFire to follow these next steps.

A Hosted Graphite account will provide the data source, offer an alerting feature, and include Hosted Grafana as a visualization tool.

To configure the Graphite output, locate the downloaded telegraf configuration file at /etc/telegraf/telegraf.conf and open it in your preferred text editor. Then, you will need to make the following changes to the file:

First, uncomment the line:

[[outputs.graphite]]

Next, uncomment and edit the server line to:

servers = ["carbon.hostedgraphite.com:2003"]

Finally, uncomment and edit the prefix line to:

prefix = "<YOUR_API_KEY>.telegraf"
If you don't already have a Hosted Graphite account, sign up for a free trial here to obtain a Hosted Graphite API key.
Otherwise, you can configure a different telegraf output to forward metrics to another data source.

Configure the PostgreSQL Input Plugin:

Telegraf has many input plugins that can collect a wide range of data from many popular technologies and 3rd party sources. In this example, we'll demonstrate how to configure the Postgresql plugin.

All you need to do is search for the inputs. postgresql section in your telegraf.conf file, and uncomment the [[inputs.postgresql]] line:

[[inputs.postgresql]]

Then you can specify an address URL or uncomment the 'address' line for localhost:

address = "host=localhost user=postgres sslmode=disable"

Save your changes, and then run Telegraf using the following command to see if there are any configuration errors in the output:

telegraf --config telegraf.conf

NOTE: if your Telegraf config contains the default user=postgres, you should create this same user in your DB:

createuser -s postgres

Telegraf will now be forwarding roughly 27 metrics per DB/user to your data source; this is what they will look like in the Graphite format:

telegraf.<host>.postgres.host=localhost_user=postgres_.postgresql.blk_read_time
telegraf.<host>.postgres.host=localhost_user=postgres_.postgresql.blk_write_time
telegraf.<host>.postgres.host=localhost_user=postgres_.postgresql.blks_hit
telegraf.<host>.postgres.host=localhost_user=postgres_.postgresql.blks_read
telegraf.<host>.postgres.host=localhost_user=postgres_.postgresql.buffers_alloc
telegraf.<host>.postgres.host=localhost_user=postgres_.postgresql.buffers_backend
telegraf.<host>.postgres.host=localhost_user=postgres_.postgresql.buffers_backend_fsync
telegraf.<host>.postgres.host=localhost_user=postgres_.postgresql.buffers_checkpoint
telegraf.<host>.postgres.host=localhost_user=postgres_.postgresql.buffers_clean
telegraf.<host>.postgres.host=localhost_user=postgres_.postgresql.checkpoint_sync_time
telegraf.<host>.postgres.host=localhost_user=postgres_.postgresql.checkpoint_write_time
telegraf.<host>.postgres.host=localhost_user=postgres_.postgresql.checkpoints_req
telegraf.<host>.postgres.host=localhost_user=postgres_.postgresql.checkpoints_timed
telegraf.<host>.postgres.host=localhost_user=postgres_.postgresql.conflicts
telegraf.<host>.postgres.host=localhost_user=postgres_.postgresql.datid
telegraf.<host>.postgres.host=localhost_user=postgres_.postgresql.deadlocks
telegraf.<host>.postgres.host=localhost_user=postgres_.postgresql.maxwritten_clean
telegraf.<host>.postgres.host=localhost_user=postgres_.postgresql.numbackends
telegraf.<host>.postgres.host=localhost_user=postgres_.postgresql.temp_bytes
telegraf.<host>.postgres.host=localhost_user=postgres_.postgresql.temp_files
telegraf.<host>.postgres.host=localhost_user=postgres_.postgresql.tup_deleted
telegraf.<host>.postgres.host=localhost_user=postgres_.postgresql.tup_fetched
telegraf.<host>.postgres.host=localhost_user=postgres_.postgresql.tup_inserted
telegraf.<host>.postgres.host=localhost_user=postgres_.postgresql.tup_returned
telegraf.<host>.postgres.host=localhost_user=postgres_.postgresql.tup_updated
telegraf.<host>.postgres.host=localhost_user=postgres_.postgresql.xact_commit
telegraf.<host>.postgres.host=localhost_user=postgres_.postgresql.xact_rollback

See the official GitHub repository for more information and configuration options for the Postgresql input plugin.

Use Hosted Graphite by MetricFire to Create Custom Dashboards and Alerts

MetricFire is a monitoring platform that enables you to gather, visualize, analyze, and alert on metrics from sources such as servers, databases, networks, devices, and applications. Using MetricFire, you can effortlessly identify problems and optimize resources within your infrastructure. Hosted Graphite by MetricFire removes the burden of self-hosting your monitoring solution, allowing you more time and freedom to work on your most important tasks.

  1. Once you have signed up for a Hosted Graphite account and used the above steps to configure your server with the Telegraf Agent, metrics will be forwarded, timestamped, ingested, and aggregated into the Hosted Graphite backend.
  2. They will be sent and stored in the Graphite format of metric.name.path <numeric-value> <unix-timestamp> provides a tree-like data structure and makes them easy to query.
  3. These metrics can be found in your Hosted Graphite account, where you can use them to build custom Alerts and Grafana dashboards.

Create Dashboards in Hosted Graphite's Hosted Grafana

In the Hosted Graphite UI, navigate to Dashboards => Primary Dashboards and select the + button to build a new panel:

How to Monitor PostgreSQL With Telegraf and MetricFire - 1

Then you can use the query UI to select a graphite metric path (the default data source will be the hosted graphite backend if you are accessing Grafana through your Hosted Graphite account):

 

The Hosted Graphite datasource also supports wildcard (*) searches to grab all metrics that match a specified path.

How to Monitor PostgreSQL With Telegraf and MetricFire - 2

Now you can apply Graphite functions to these metrics, like aliasByNode(), to reformat the metric names on the graph:

How to Monitor PostgreSQL With Telegraf and MetricFire - 3

Grafana has many additional options, like configuring dashboard variables and annotations. You can also use different visualizations, modify the display, set the units of measurement, and much more.

Hosted Graphite also has a pre-configured dashboard for Telegraf metrics located in their Dashboard Library:

How to Monitor PostgreSQL With Telegraf and MetricFire - 4

Once this dashboard is generated in your account, you can locate it in your Primary Dashboards to see system metrics (CPU, mem, disk) displayed.

These system performance metrics come standard with a Telegraf => Graphite configuration:

How to Monitor PostgreSQL With Telegraf and MetricFire - 5

See the Hosted Graphite dashboard docs for more details.

Creating Graphite Alerts

In the Hosted Graphite UI, navigate to Alerts => Graphite Alerts to create a new alert. Name the alert, add one of your graphite metrics to the alerting metric field, and add a description of what this alert is:

How to Monitor PostgreSQL With Telegraf and MetricFire - 6

Then, select the Criteria tab, which will set the threshold, and select a notification channel. The default notification channel is the email you used to sign up for the Hosted Graphite account. Still, you can easily configure a channel for Slack, PagerDuty, Microsoft Teams, and more. See the Hosted Graphite docs for more details on notification channels:

How to Monitor PostgreSQL With Telegraf and MetricFire - 7

Conclusion

Database monitoring is crucial for businesses as it ensures critical data infrastructure's optimal performance, reliability, and security. Businesses can proactively identify and address potential issues before they impact operations by tracking key metrics such as resource utilization, query performance, and system health. Monitoring facilitates efficient capacity planning, enabling businesses to scale resources appropriately and avoid downtime due to resource shortages. It is pivotal in ensuring data integrity, security compliance, and user satisfaction. Additionally, by analyzing patterns and trends over time, businesses can make informed decisions for database optimization, cost management, and strategic planning, ultimately contributing to their operations' overall stability and success.

DB performance monitoring provides valuable data, and using tools like dashboards and alerts complements this monitoring by providing real-time visualization, proactive identification of issues, historical trend analysis, and facilitating informed decision-making, all of which are essential for maintaining a robust and efficient network infrastructure.

Sign up for a free trial, and experiment with monitoring your PostgreSQL instances today! You can also book a demo and talk to the MetricFire team directly about your monitoring needs.

You might also like other posts...
metricfire Dec 06, 2024 · 6 min read

Step by Step Guide to Monitoring Apache Spark with MetricFire

Monitoring Spark metrics is crucial because it provides visibility into how your cluster and... Continue Reading

metricfire Dec 02, 2024 · 8 min read

Easiest Way to Monitor Your API Endpoints Using Telegraf

Monitoring the health of your API endpoints is crucial to keeping your applications running... Continue Reading

metricfire Nov 28, 2024 · 3 min read

厳選!オープンソースのネットワーク監視ツール

ネットワーク監視は、組織に影響を及ぼす可能性のあるネットワーク関連の問題について貴重な洞察を提供する、ネットワーク管理戦略の重要な要素です。ネットワークを定期的に監視することで、ネットワークの過負荷、ルーターの問題、ダウンタイム、サイバー犯罪、データ損失などのリスクを軽減します。 Continue Reading

header image

We strive for 99.999% uptime

Because our system is your system.

14-day trial 14-day trial
No Credit Card Required No Credit Card Required