Graphite Integration
Receive Carbon plaintext and pickle protocol metrics for legacy system support. TigerOps ingests your Graphite streams natively and adds AI anomaly detection, dimensional labels, and modern alerting.
How It Works
Configure Carbon Relay
Point your existing Carbon relay or graphite-agent to the TigerOps Carbon receiver endpoint on port 2003 (plaintext) or 2004 (pickle). No schema changes required.
Verify Metric Ingestion
TigerOps accepts the standard Carbon line format: <metric.path> <value> <timestamp>. Check the live tail in your TigerOps workspace to confirm metrics are arriving.
Map Dotted Paths to Labels
Configure extraction rules to convert Graphite dotted metric paths into structured labels. TigerOps auto-suggests label mappings based on your metric hierarchy.
Build Dashboards and Alerts
Use your existing Graphite metric names in TigerOps dashboards. Set anomaly-based alerts that replace static thresholds with AI-learned baselines for each metric.
What You Get Out of the Box
Carbon Plaintext & Pickle Support
Native receiver for both Carbon plaintext (TCP port 2003) and binary pickle protocol (TCP port 2004). Drop-in replacement for your existing Graphite cluster without client-side changes.
Dotted Path Label Extraction
Automatically parse Graphite dotted metric paths (servers.web01.cpu.idle) into structured dimensional labels. Define extraction templates with positional or regex-based rules.
Pickle Batch Ingestion
Handle high-throughput pickle protocol batches from Carbon-relay and carbon-c-relay. TigerOps decodes and decompresses batches with backpressure-aware ingestion to prevent data loss.
Legacy Metric Retention Migration
Import historical Whisper (.wsp) file data into TigerOps long-term storage. Preserve retention policies during migration so your historical baselines remain intact.
Graphite Function Compatibility
TigerOps query layer supports common Graphite render functions (summarize, movingAverage, derivative, scale) so existing dashboards migrate without query rewrites.
AI Anomaly Detection on Carbon Streams
TigerOps applies per-metric seasonal models to Carbon streams, detecting anomalies that static Graphite alert rules would miss — including gradual drift and multi-metric correlations.
Carbon Relay Forwarding Config
Forward your existing Carbon metrics to TigerOps using carbon-c-relay.
# carbon-c-relay configuration to forward to TigerOps
# Install: https://github.com/grobian/carbon-c-relay
# Local Carbon receiver (your existing Graphite agents point here)
listen plaintext :2003
listen pickle :2004
# Forward all metrics to TigerOps Carbon receiver
cluster tigerops
forward
ingest.atatus.net:2003
;
# Route everything to TigerOps
match *
send to tigerops
stop
;
# Optional: extract labels from dotted metric paths
# servers.{host}.{subsystem}.{metric} -> host, subsystem labels
# Configure extraction in TigerOps UI under Settings > Label Extraction
# TigerOps Carbon receiver endpoints:
# Plaintext TCP: ingest.atatus.net:2003
# Pickle TCP: ingest.atatus.net:2004
# API key auth: Set X-TigerOps-Key header via proxy or use TLS SNI auth
# Whisper historical data import:
# tigerops-import whisper --dir /var/lib/graphite/whisper \
# --endpoint https://ingest.atatus.net \
# --api-key ${TIGEROPS_API_KEY}Common Questions
Does TigerOps support the Graphite pickle protocol in addition to plaintext?
Yes. TigerOps exposes a Carbon-compatible receiver on port 2004 for the binary pickle protocol. The receiver handles batched pickle payloads from carbon-relay, carbon-c-relay, and StatsD forwarders without any client modifications.
Can I migrate historical Whisper data to TigerOps?
Yes. TigerOps provides a whisper-import CLI tool that reads .wsp files and backfills the data into TigerOps long-term storage. Run it alongside a live Carbon relay so you capture both historical and new data simultaneously.
How does TigerOps handle Graphite dotted metric paths?
TigerOps auto-extracts labels from dotted paths using configurable extraction rules. For example, servers.web01.cpu.idle can become {host="web01", metric="cpu.idle"}. You can define templates via the UI or a YAML config file.
What happens if the TigerOps Carbon receiver is temporarily unavailable?
We recommend placing a carbon-c-relay or carbon-relay-ng in front of TigerOps with a disk-backed queue. This buffers metrics locally during brief connectivity interruptions and replays them once the connection is restored.
Can TigerOps ingest metrics from StatsD alongside Carbon?
Yes. TigerOps supports StatsD UDP input on port 8125 concurrently with Carbon. Metrics from both sources land in the same workspace where you can correlate them in unified dashboards.
Modernize Your Graphite Metrics Without a Rewrite
Keep your Carbon agents. Gain AI anomaly detection, dimensional labels, and modern alerting. Deploy in minutes.