| To: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] pmmgr pmlogger default behaviour |
| From: | "Frank Ch. Eigler" <fche@xxxxxxxxxx> |
| Date: | Thu, 30 Jan 2014 15:36:52 -0500 |
| Cc: | "'Nathan Scott'" <nathans@xxxxxxxxxx>, "'pcp developers'" <pcp@xxxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <06a301cf1df4$d18984b0$749c8e10$@internode.on.net> |
| References: | <2108905700.15892281.1391033827018.JavaMail.root@xxxxxxxxxx> <1583484726.15908616.1391037005341.JavaMail.root@xxxxxxxxxx> <06a301cf1df4$d18984b0$749c8e10$@internode.on.net> |
| User-agent: | Mutt/1.4.2.2i |
Hi - > [...] I think the archive (especially with rsync) considerations > favour only updating/creating files for today's data each day. [...] By the way, as we don't provide any off-machine archiving facilities such as rsync, the default for archive collection need not be a perfect match for that scenario. We don't need to especially cater to such elaborate configurations *in our defaults*. For those sites that wish to move archives and use pmmgr, they just need to # rm /etc/pcp/pmmgr/pmlogmerge to disable the limited automation there now, and get individual files that they may move / aggregate / etc. how they wish. So it's not a big hurdle. - FChE |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] pmmgr pmlogger default behaviour, Frank Ch. Eigler |
|---|---|
| Next by Date: | Re: pmmgr pmlogger default behaviour, Nathan Scott |
| Previous by Thread: | Re: [pcp] pmmgr pmlogger default behaviour, Frank Ch. Eigler |
| Next by Thread: | Re: [pcp] pmmgr pmlogger default behaviour, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |