---
title: Push to Graphite
description: Deprecated. Configure PingDS to push monitoring metrics to Graphite using the Graphite Monitor Reporter plugin.
component: pingds
version: 7.5
page_id: pingds:monitoring-guide:graphite
canonical_url: https://docs.pingidentity.com/pingds/8.1/monitoring-guide/graphite.html
llms_txt: https://docs.pingidentity.com/pingds/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: 2023-08-10T15:45:40Z
keywords: ["Monitoring"]
superseded_by: https://docs.pingidentity.com/pingds/8.1/monitoring-guide/graphite.html
---

# Push to Graphite

The [Graphite](https://graphiteapp.org/) application stores numeric time-series data of the sort produced by monitoring metrics, and allows you to render graphs of that data.

Your applications, in this case DS servers, push data into Graphite. You do this by configuring the [Graphite Monitor Reporter Plugin](../configref/objects-graphite-monitor-reporter-plugin.html) with the host and port number of the Graphite service, and with a prefix for your server, such as its FQDN. By default, the plugin pushes all metrics it produces to the Graphite service. You can opt to limit this by setting the `excluded-metric-pattern` or `included-metric-pattern` properties.

The following example configures the plugin to push metrics to Graphite at `graphite.example.com:2004` every 10 seconds (default):

```bash
$ dsconfig \
 create-plugin \
 --hostname localhost \
 --port 4444 \
 --bindDN uid=admin \
 --bindPassword password \
 --plugin-name Graphite \
 --type graphite-monitor-reporter \
 --set enabled:true \
 --set graphite-server:graphite.example.com:2004 \
 --set metric-name-prefix:ds.example.com \
 --usePkcs12TrustStore /path/to/opendj/config/keystore \
 --trustStorePassword:file /path/to/opendj/config/keystore.pin \
 --no-prompt
```

To view metrics stored in Graphite, you can use the Graphite render API or [Grafana](https://grafana.com/), for example. Refer to the Graphite and Grafana documentation for details.