graphite-dev team mailing list archive

[Amelia Hansen <question171056@xxxxxxxxxxxxxxxxxxxxx>]

Question #171056 on Graphite changed:
https://answers.launchpad.net/graphite/+question/171056

Amelia Hansen posted a new comment:
Andrew's challenge involves updating his company's Graphite version
while maintaining their existing "load on demand" data retrieval from
the stats server. Here are some potential solutions:

Migrate to newer Graphite version with customization:
Use Graphite web app interface: While the Reader/Finder interface is gone, the newer one provides APIs for fetching data on demand. Implement scripts in your stats server to call these APIs instead of using the old "readers.py" and "finders.py" approaches. This lets you 
keep Graphite for graphing without pushing data to Carbon.

Customize Carbon data pipeline: Set up Carbon as a receiver but configure it to only store aggregated data (not raw data) to minimize redundancy. Consider using Carbon's whisper database API to query aggregated data from your stats server directly, bypassing the continuous push.
You can also read it here: https://bartlebyandsage.com/

-- 
You received this question notification because your team graphite-dev
is an answer contact for Graphite.