It first needs a sponsor from a wmf staff.

FWIW, This access is quite sensitive.

Hi @jeremyb Thanks for checking in. We have sunsetted the L2 form. I am happy to facilitate an NDA from my end though. Please send your full name, email address, mailing address, and a few details about the access you'll need to kfrancis@wikimedia.org and I'll process an NDA for you to sign.

so I can detect when I am spamming the logs before I disrupt the deployment train

The logspam checker script comes to mind when reading this.

Are you aware of https://gerrit.wikimedia.org/g/operations/puppet/+/refs/changes/21/1056221/3/modules/role/files/logging/logspam.pl already?

This could be a fix for this that only requires one of the following shell groups to get to mwlog1002.

profile::admin::groups:
  - deployment
  - restricted
  - mw-log-readers

Since you say "before I disrupt the deployment train" it sounds like you already have deployment access and this should come with it.

In T374406#10133385, @Ladsgroup wrote:

It first needs a sponsor from a wmf staff.

ok, I had some ideas of people to ask but I'm still trying to figure out what the criteria are exactly besides "wmf staff". I started with @Dzahn for continuity because he was involved with my NDA last time.

In T374406#10135229, @Dzahn wrote:

Since you say "before I disrupt the deployment train" it sounds like you already have deployment access and this should come with it.

No, I don't have shell access currently. maybe logstash wasn't exactly the right request but it came to mind since I had access to it previously and because that's where @Jdlrobson copied the stack trace from.

That was a reference to when I disrupted the train yesterday documented in T374394: TypeError: tests.values().toArray is not a function (Wikicurious_beat_en).