I like this idea but I would opt for json or yamls, right now json is being widely accepted and the overhead is really low compared to xml.
Just my two cents Regards On Thu, Jan 27, 2011 at 11:21 AM, John Feuerstein <j...@feurix.com> wrote: >> That's what we'd all like. Currently the CSV lacks some information >> compared to the HTML. But we can't export everything in it without >> breaking its simple format, and breaking it is out of questions. So >> my goal is to have a "detailed" version of the CSV that would use >> quotes to delimit strings, and that more advanced parsers will be >> able to use. > > Just as an idea: What do you think about an additional XML stats output > format? The CSV could stay backwards compatible with basic/technical > information only, while the XML format could be (similar to the HTML/XHTML) > configurable with custom fields. It would prevent breaking parsers even if > haproxy itself adds new fields in the future. The data could be grouped > logically, no need to store identifiers multiple times... > > Best, > John > > -- Gabriel Sosa Si buscas resultados distintos, no hagas siempre lo mismo. - Einstein
