duplicity-team team mailing list archive
-
duplicity-team team
-
Mailing list archive
-
Message #01569
Re: [Question #219277]: I don't fully understand the format of log-file. And how about add JSON-formatted log files?
Question #219277 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/219277
Status: Open => Answered
edso proposed the following answer:
On 15.01.2013 23:01, Chaser-andrey wrote:
> New question #219277 on Duplicity:
> https://answers.launchpad.net/duplicity/+question/219277
>
> What the magic numbers in the log files?
> NOTICE 1
> WARNING 1
> WARNING 5
> INFO 3
which magic numbers? generally there are several log levels, see manpage.
> I can't found any docs about structure of log files. :-(
there are two kinds of log output.
1. the user interpretable (default), which is generally a text about
what is going on with a note about the severance (log level)
2. --log-file <filename>, --log-fd <number> enable additional simplified
output .. pretty much like the above but formatted for easier parsing.
unfortunately there is no specific documentation about it, but try it
and compare it to the default out and you'll understand.
> Also, what about adding optional support for JSON format of log files?
I see in documentation, that log files "designed to be easily consumable
by other programs." I think that JSON format will be much better and
easily, because there are many light and fast JSON parsers for different
languages.
that's not an option for light weight backends like the bash based shell
one duply i am maintaining. so yes, as an addition, no as a replacement.
> I'm not a Python developer, but I think, I'll might write patch if upstream will support this idea.
>
>
you are welcome to do so, i suggest you to add a --log-format
[plain,json] switch, plain being the default value.
..ede/duply.net
--
You received this question notification because you are a member of
duplicity-team, which is an answer contact for Duplicity.