On Tue, 2007-11-06 at 13:23 -0600, [EMAIL PROTECTED] wrote:
> - Provide graphs as a web service
> This would accept requests for metric data (XML, JSON, whichever),
> generate a graph, and respond with a URL to the graph. This would
> make it possible to embed metrics in other web application
Hi Alex,
Some thoughts...
On Tuesday 06 November 2007 20:23:50 [EMAIL PROTECTED] wrote:
> I've been working on a list of ways to improve the PHP web frontend.
> Just curious what every else thinks of these.
>
> - add support for a caching layer for generated graphs
> Add code that allows caching
Matthew Chambers wrote:
I don't know if I would call it difficult change, but it's a different
method of generating the graph. Currently rrdtool writes to standard
output and that gets sent straight to the client (after the HTTP
I'd forgotten that the graphs were generated on the fly. That
I don't know if I would call it difficult change, but it's a different
method of generating the graph. Currently rrdtool writes to standard
output and that gets sent straight to the client (after the HTTP
header). The --lazy option obviously only works for writing to a file,
which means the f
[EMAIL PROTECTED] wrote:
I've been working on a list of ways to improve the PHP web frontend.
Just curious what every else thinks of these.
- add support for a caching layer for generated graphs
Add code that allows caching of generated graphs, either on the
filesystem or in a memcache cach
I've been working on a list of ways to improve the PHP web frontend.
Just curious what every else thinks of these.
- add support for a caching layer for generated graphs
Add code that allows caching of generated graphs, either on the
filesystem or in a memcache cache. When generating a graph
