A Passionate Techie

Ceres is a time-series database format intended to replace Whisper as the default storage format for Graphite. In contrast with Whisper, Ceres is not a fixed-size database and is designed to better support sparse data of arbitrary fixed-size resolutions. This allows Graphite to distribute individual time-series across multiple servers or mounts. Ceres is not actively developped at the moment. For alternatives to whisper look at  alternative storage backends . Storage Overview Ceres databases are comprised of a single tree contained within a single path on disk that stores all metrics in nesting directories as nodes. A Ceres node represents a single time-series metric, and is composed of at least two data files. A slice to store all data points, and an arbitrary key-value metadata file. The minimum required metadata a node needs is a  'timeStep' . This setting is the finest resolution that can be used for writing. A Ceres node however can contain and read data with other...

Ceres is a time-series database format intended to replace Whisper as the default storage format for Graphite. In contrast with Whisper, Ceres is not a fixed-size database and is designed to better support sparse data of arbitrary fixed-size resolutions. This allows Graphite to distribute individual time-series across multiple servers or mounts. Ceres is not actively developped at the moment. For alternatives to whisper look at  alternative storage backends . Storage Overview Ceres databases are comprised of a single tree contained within a single path on disk that stores all metrics in nesting directories as nodes. A Ceres node represents a single time-series metric, and is composed of at least two data files. A slice to store all data points, and an arbitrary key-value metadata file. The minimum required metadata a node needs is a  'timeStep' . This setting is the finest resolution that can be used for writing. A Ceres node however can contain and read data with other, less-p...

Getting your data into Graphite is very flexible. There are three main methods for sending data to Graphite: Plaintext, Pickle, and AMQP. It’s worth noting that data sent to Graphite is actually sent to the  Carbon and Carbon-Relay , which then manage the data. The Graphite web interface reads this data back out, either from cache or straight off disk. Choosing the right transfer method for you is dependent on how you want to build your application or script to send data: There are some tools and APIs which can help you get your data into Carbon. For a singular script, or for test data, the plaintext protocol is the most straightforward method. For sending large amounts of data, you’ll want to batch this data up and send it to Carbon’s pickle receiver. Finally, Carbon can listen to a message bus, via AMQP. The plaintext protocol The plaintext protocol is the most straightforward protocol supported by Carbon. The data sent must be in the following format:  <me...

Getting your data into Graphite is very flexible. There are three main methods for sending data to Graphite: Plaintext, Pickle, and AMQP. It’s worth noting that data sent to Graphite is actually sent to the  Carbon and Carbon-Relay , which then manage the data. The Graphite web interface reads this data back out, either from cache or straight off disk. Choosing the right transfer method for you is dependent on how you want to build your application or script to send data: There are some tools and APIs which can help you get your data into Carbon. For a singular script, or for test data, the plaintext protocol is the most straightforward method. For sending large amounts of data, you’ll want to batch this data up and send it to Carbon’s pickle receiver. Finally, Carbon can listen to a message bus, via AMQP. The plaintext protocol The plaintext protocol is the most straightforward protocol supported by Carbon. The data sent must be in the following format:  <metric   path> ...

What Graphite is and is not Graphite does two things: Store numeric time-series data Render graphs of this data on demand What Graphite does not do is collect data for you, however there are some  tools  out there that know how to send data to graphite. Even though it often requires a little code,  sending data  to Graphite is very simple. About the project Graphite is an enterprise-scale monitoring tool that runs well on cheap hardware. It was originally designed and written by  Chris Davis  at  Orbitz  in 2006 as side project that ultimately grew to be a foundational monitoring tool. In 2008, Orbitz allowed Graphite to be released under the open source Apache 2.0 license. Since then Chris has continued to work on Graphite and has deployed it at other companies including  Sears , where it serves as a pillar of the e-commerce monitoring system. Today many large  companies  use it. The architecture in a nutshell Grap...

What Graphite is and is not Graphite does two things: Store numeric time-series data Render graphs of this data on demand What Graphite does not do is collect data for you, however there are some  tools  out there that know how to send data to graphite. Even though it often requires a little code,  sending data  to Graphite is very simple. About the project Graphite is an enterprise-scale monitoring tool that runs well on cheap hardware. It was originally designed and written by  Chris Davis  at  Orbitz  in 2006 as side project that ultimately grew to be a foundational monitoring tool. In 2008, Orbitz allowed Graphite to be released under the open source Apache 2.0 license. Since then Chris has continued to work on Graphite and has deployed it at other companies including  Sears , where it serves as a pillar of the e-commerce monitoring system. Today many large  companies  use it. The architecture in a nutshell Graphite consists of 3 software components: carbon  - a  Twisted  dae...