on-call_guy

4 ms·

1.
by on-call_guy 3y ago
Ok great. will take a look
2.
by on-call_guy 3y ago
Ok, thanks. Is there a limit on how many alerts we can get in this Slack report?
3.
by on-call_guy 3y ago
Interesting. How is it different from PagerDuty offered integration with Slack? We can get notifications from Pagerduty right?
4.
Is there a way to download on-call report with incident summary from Pagerduty?
1 points by on-call_guy 3y ago|0 comments
5.
by on-call_guy 3y ago
Yep, we do this in our team too (day time only though) and call it as "on-call buddy" for first couple of rotations.
6.
by on-call_guy 3y ago
I see...how does it really work though? Like if I am on-call for this week- would it show all my alerts in one place and then allow me to take some kind of actions? How does it solve the other issues like stale runbooks, etc?
7.
by on-call_guy 3y ago
Got it. I wish there was an up to date service level owner identified which will then reduce this to just a lookup and tagging. I have seen few engineering teams in other companies started doing that.
8.
by on-call_guy 3y ago
Yeah, JIRA could be handy and useful though you need to create tickets for every tasks with a rigorous monitoring with other backlog and story items.
9.
by on-call_guy 3y ago
Thanks for the link. It doesn't have much details. I have signed up though. Looking forward for getting more details about the solutions.
10.
by on-call_guy 3y ago
lol...yeah we have that established within the team now. But still a challenge to find out a right contact across teams at 3am in the morning if the issue is from another team. May be we should build a service level ownership list so that w
11.
by on-call_guy 3y ago
I agree they can be improved. But they are not one-time activity. It should be a continuous process in order to really be efficient. Also every on-call person needs to be diligent about it. Otherwise, it aggregates in future. Again, I am ta
12.
by on-call_guy 3y ago
Ok...Would love to know more about what is out there. The problem with current alerting solutions like PagerDuty, they are every extensive in terms of what they offer (scheduling, reliability, etc) but not quite tailored towards needs of on
13.
by on-call_guy 3y ago
That's great. I think one of the issue in our process is we use wiki for on-call summary/hand-off notes. That's not ALWAYS very helpful as it has a dependency what engineers add to them. Also time and severity of the alerts m
14.
by on-call_guy 3y ago
Yeah, I must agree it is a cultural issue at some extent. But honestly the on-call my current company is quite demanding. So during the on-call week, though engineers try to improve it they always run out of the time or miss few things whic
15.
by on-call_guy 3y ago
Thank you. Its a great point and totally agree that a good management plays a big role in making life little easy. We did raise it to our management. But one of the limitations from their end is as well too many different tools and scattere
16.
On-call problems – here are mine. Do you feel the same way?
9 points by on-call_guy 3y ago|28 comments
17.
by on-call_guy 3y ago
Looks great