+1 on the piping logs into some nice interface. Would solve a lot of the problems we have been looped in on.
On Tuesday, January 13, 2015, Nuria <[email protected]> wrote: > Kevin: > > The logs in question have always required sudo. I just changed permits > before by hand so they were visible to all users. > > Permits are set up by the puppet setup of EL which is identical in beta > labs and production. > > Thanks, > > Nuria > > On Jan 13, 2015, at 2:58 PM, Ryan Kaldari <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: > > On Tue, Jan 13, 2015 at 2:50 PM, Kevin Leduc <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: > >> Access permisions >> What's the machine and the log you're trying to access (please be >> specific, I am not a developer so assume I know very little). I'll pass >> this on to Ops so they can have a look at why permissions changed. This >> shouldn't happen. >> > > The logs are > /var/log/upstart/eventlogging_processor-client-side-events.log and > /var/log/upstart/eventlogging_processor-server-side-events.log on > deployment-eventlogging02. I have now been given sudo on this machine, so > it isn't an issue anymore for me personally, but it would be great if other > developers could access these logs for debugging purposes. > > >> Piping Events that fail validation. >> It's in our backlog, it's relatively high priority, but not high enough >> for us to have tasked it out yet or committed it to a sprint. That'll >> happen in February. >> > > That sounds great. Thanks for the update! > > Kaldari > > > > _______________________________________________ > Analytics mailing list > [email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');> > https://lists.wikimedia.org/mailman/listinfo/analytics > >
_______________________________________________ Analytics mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/analytics
