Ahem.... they are there: nuria@deployment-eventlogging02:/var/log/upstart$ ls eventlogging_*log eventlogging_processor-client-side-events.log eventlogging_processor-server-side-events.log On Wed, Jan 7, 2015 at 12:57 PM, Ryan Kaldari <rkaldari(a)wikimedia.org> wrote: _______________________________________________ Analytics mailing list Analytics(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics

Looks like I've lost permission to view those logs on Beta Labs again. Any

Also, was any progress ever made on piping the live cluster errors into a

Looks like I've lost permission to view those logs on Beta Labs again. Any chance you could fix them? Also, was any progress ever made on piping the live cluster errors into a dedicated log with easy access? I know it sounds like it wouldn't be that useful, but we have actually had cases where server-side EventLogging was failing on en.wiki, but working on Beta Labs and locally. It would also be useful for catching obscure failures that only happen for edge cases. Kaldari On Wed, Jan 7, 2015 at 1:27 PM, Ryan Kaldari <rkaldari(a)wikimedia.org> wrote: _______________________________________________ Analytics mailing list Analytics(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/analytics

On Sun, Jan 11, 2015 at 5:28 PM, Nuria Ruiz <nuria(a)wikimedia.org> wrote: It seems a bit silly for me to ask for sudo just so I can occasionally look at some logs, but I'll go ahead and do that.

I don't remember that being the outcome of our meeting. I don't even have

look at some logs, but I'll go ahead and do that. Much agree, it is unfortunate that is the state of affairs. have access to stat1002, much less vanadium. I only >have access to stat1003. I'll try asking for access to those servers as well, but ideally I would like for all the developers on my >team to have access to an EventLogging error log for the cluster. mmmm.. that is why I think we should always have meeting notes, if someone that was also on that meeting can chime in it will be great. I might be misremembering this. Thank you, Nuria On Sun, Jan 11, 2015 at 8:51 PM, Ori Livneh <ori(a)wikimedia.org> 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.

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.

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 &lt;rkaldari(a)wikimedia.org <javascript:_e(%7B%7D,'cvml','rkaldari@wikimedia.org');>> wrote: On Tue, Jan 13, 2015 at 2:50 PM, Kevin Leduc &lt;kevin(a)wikimedia.org <javascript:_e(%7B%7D,'cvml','kevin@wikimedia.org');>> wrote: 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. That sounds great. Thanks for the update! Kaldari _______________________________________________ Analytics mailing list Analytics(a)lists.wikimedia.org <javascript:_e(%7B%7D,'cvml','Analytics@lists.wikimedia.org');> https://lists.wikimedia.org/mailman/listinfo/analytics