LinkedIn Open Sources a Pair of Incident-Escalation Tools

Some companies don’t always get the public credit they deserve for contributing to the open source community software and tools that can enable other developers to move their own projects along quicker and more efficiently.

Companies such as Facebook, Google and others are famous for giving back to the software community valuable code, tools and hardware designs that they can use to solve thorny problems. But others, such as Yahoo and LinkedIn, aren’t as well known for what they are contributing.

Besides the original development of Hadoop a dozen years ago, Yahoo has been an active participant in projects such as those listed on the company's Github page[1], in various Apache Software Foundation Communities, and in niche communities, such as CPAN and others.  

Last month it released a container-access control[2] to the community, a valuable tool in view of the current popularity of new-gen container/micro-services-based systems.

Mountain View, Calif.-based social network LinkedIn is now stepping up, announcing June 29 that it has open-sourced two incident-escalation tools, called Iris and Oncall; a high-level description of each is below.

LinkedIn said it has seen huge internal adoption of these tools, even from non-technical teams, such as sales. Both are designed for easy adoption by other organizations and are useful for companies ranging in size from small startups to large enterprises.

Tool 1: Iris

Previously, LinkedIn had been relying on an escalation system that required manual forwarding of alerts—a solution that obviously didn’t scale well. With Iris, LinkedIn has created a reliable messaging system that allows users to create flexible, modular escalation plans.

For example, rather than specifically defining users to escalate to, Iris supports custom roles, with pluggable methods of role lookups. It also works with multiple messaging services, including Slack, Twilio and SMS messaging.

Tool 2: Oncall

Oncall is the source from which Iris draws to determine which team members are on-call for a given scenario. It allows managers to define rotating schedules for on-call shifts and provides a calendar for viewing and changing these shifts as needed.

One of the advantages of having Oncall as a separate service is the ability to provide teams with an on-call scheduling tool without necessarily tying in escalation, for non-emergency projects.

Read this blog[3] by LinkedIn’s Daniel Wang for all the engineering details about how these two tools work and for directions on how to obtain them.

References

  1. ^ Github page (Github.com)
  2. ^ released a container-access control (www.eweek.com)
  3. ^ Read this blog (engineering.linkedin.com)

Comments

Post a Comment

Popular posts from this blog

New Article Posted: Seven Things You Should Do in Your AMS

Given how advanced and thorough the modern association management software (AMS) system has become, there are many opportunities for your organization to leverage it. Here are seven ways I believe every association should be using their AMS. Click here to read the rest of the article . Of course, if you’re already on my  announcements list , you would have received notice of this new article right in your email box. Not signed up yet?  Click here to sign up . Go to the article
Read more

10 Common Mistakes Biblical Counselors Sometimes Make, Part 8

Image
A Word from Bob: You’re reading Part 8 of a 10-part blog series on 10 Common Mistakes Biblical Counselors Sometimes Make . Mistake #1: We Elevate Data Collection Above Soul Connection . Mistake #2: We Share God’s Eternal Story Before We Listen Well and Wisely to Our Friend’s Earthly Story . Mistake #3: We Talk at Counselees Rather Than Exploring Scriptures with Counselees . Mistake #4: We Practice Half-Biblical Counseling If We Address Sin but Neglect Suffering . Mistake #5: We Fail to Follow the Trinity’s Model of Comforting Care . Mistake #6: We Tend to View People One-Dimensionally . Mistake #7: We Devalue Emotions Rather Than Seeing Emotions as God’s Idea . Mistake #8: We Minimize the Complexity of the Soul-Body Interconnection Because we are soul physicians and soul care-givers, our tendency is to focus on matters of the soul. Most biblical counselors are not trained in the medical field, so we wisely avoid offering medical guidance. Yet, that appropr
Read more