Contact Information

Include contact information so anyone can quickly determine who to can contact and how to contact them if they have a problem or need to ask a question.

List Your Preferred Method of Communication

If you have a preferred method of communication, make sure to list it here and provide any instructions needed to use or access that method.

Also, provide on-call information so everyone knows exactly who to contact in an emergency situation. If a product specifies an SLA or level of support, (e.g. immediate support during business hours Eastern time, but only best after outside those hours) list that here.

If an on-call rotation is established, enter it here. If a managed service provider is being used, make sure to detail how to contact them. If the client is providing support, that information should be listed. If none of these are in place, then it is time to have a conversation to determine a support strategy.

Build Production Ready Products to Avoid 2AM Alerts

On-call rotations are a necessary evil, but the best way to make being on-call painless is to build a production ready product. A production ready product is one that is: stable, reliable, scalable, fault tolerant, prepared for catastrophes, performant, monitored, and documented. For more information check out Production Ready Microservices by Susan J. Fowler. O'Reilly. 2016.

Example

Slack

Please use slack to reach out to the team and only use email if necessary or to send meeting invites.

• Domain

  • nebuchadnezzar.slack.com

• Channels

  • #production-ready-docs

  • #production-ready-docs-dev

Team Members

Name	Role	Email
Morpheus	Program Manager	[e-mail]
Neo	Dev	[e-mail]
Trinity	Dev	[e-mail]
Mouse	Dev	[e-mail]
Cypher	Dev	[e-mail]
Smith	SRE	[e-mail]

On-Call Rotation

• Even days: Neo

• Odd days: Smith