Can you provide more detailed documentation on what carbonmem do and how to use it?
What I have found is just "memory-backend carbon store", but I didn't find how to set storage schema. What's the difference with using tmpfs as go-carbon storage backend? Can you provide in what scenarios carbonmem is supposed to be used?
I have a scenario in which I would like to use memory as storage backend, but I'm not sure carbonmem is designed for that. I'm setting up a monitoring system which uses graphite stack as datasource. Since most queries are dedicated to the latest 10 minutes' data, I would love to force cache the latest 10 minutes' data of all metrics. I have the following setups in mind, but not sure which is best, or is there any even better solution?
Let carbon relay to forward two copies, one to a storage for persistence, another to go-carbon+tmpfs, with default retention policy set to 10min. All monitoring queries are directed to the latter go-carbon.
Similarly, but replace go-carbon+tmpfs with carbonmem, but I don't know if carbonmem is designed for this case. Which is what I created this issue for.
Is it possible to embed such kind of cache within go-carbon so that I don't need to let carbon relay to forward two copies. (Maybe I should create an issue for this in go-carbon project.)
Can you provide more detailed documentation on what carbonmem do and how to use it?
What I have found is just "memory-backend carbon store", but I didn't find how to set storage schema. What's the difference with using tmpfs as go-carbon storage backend? Can you provide in what scenarios carbonmem is supposed to be used?
I have a scenario in which I would like to use memory as storage backend, but I'm not sure carbonmem is designed for that. I'm setting up a monitoring system which uses graphite stack as datasource. Since most queries are dedicated to the latest 10 minutes' data, I would love to force cache the latest 10 minutes' data of all metrics. I have the following setups in mind, but not sure which is best, or is there any even better solution?