[Done] Access to Monitoring

Community Ops
#1

I’d like the infra module peers to have access to the monitoring tools.

Right now @tanner is the only person with admin access to VictorOps as far I’m aware (that being at least one tool, I’ve heard we have an uptime robot account recently), which shouldn’t be the case.

Would be great if Yousef and I could get access to all monitoring tools, so we can also work on things. As a module, it’s important all the owners/peers have access to the tools, so we can distribute workload, and for the sake of making sure things can be done in the most efficient time frame.

So, @tanner, please could you give myself and Yousef access to all the monitoring tools. As we’ve discussed before, changes made will be processed based on approval through the system we agreed on back when I first took ownership of infra (which is a process I’m documenting right now, and once documented, I expect will be followed.)

1 Like
#2

I agree with this and I’d also like @mrz to be a peer.

#3

++ to mrz as a peer, at least as a mentor/advisor to us.

@mrz happy to be listed as a peer on wiki? (or mentor?)

#4

I’d like to be an infra peer as well - I’m sure about when/how the current peers were established, but I’d like to have a large role in infra as well.

#5

Also, about monitoring tools - we currently have VictorOps fielding alerts from Pingdom and UptimeRobot (the latter of which is going away), which are both being funded by @mrz at the moment. StatusHub, too. And since they’re personal accounts, only mrz has access to them, so he has to share his account information with us.

This is obviously not an ideal situation, but there’s also sensitive information (such as his credit card number) tied to those accounts, so we need to be careful about who has access to what.

#6

Also just thought that we should extend this to things that generally need to be shared. I have a couple of passwords that the Infra team should have access to (DB, SES creds etc). Should stick them on lastpass at some point.

#7

I’d first like to see us come to a conclusion on the set of tools we’re using (to avoid tool sprawl). I’m imagining a table of tools & purpose & “owner”.

My short list right now is:

1 Like
[Done] Creating a shortlist of infra tools
#8

++ to logan as a peer. He’s been a very very core player to making our infra since the day he’s joined and I already have trusted him with the access to most of our stuff.

Unless anyone objects, I’m going to list @mrz as a mentor and @logan as a peer on the wiki.

#9

Yeah, would be great to lastpass those. Does lastpass have share groups? we should make one if it does.

#10

I moved a post to an existing topic: Creating a shortlist of infra tools

#11

The tools list seems to be mostly done. What should we do next about this topic? @mrz @logan

#12

Closed. We moved to Lastpass.

#13