The distribution team is responsible for making Sourcegraph easy to deploy, scale, monitor, and debug. We solve the most challenging problems our customers face deploying Sourcegraph on-premise in a variety of environments, and on Sourcegraph.com - the largest Sourcegraph instance in the world.
- Slack: #distributioneers channel or @distribution
- For support requests, please use our dedicated support rotation
- File issues: team/distribution label
Our team has two Slack channels, one public (#distributioneers) and one private (#distribution-team). Our default is to use the public channel. The #distribution-team channel will only be used for discussing internal team topics, like scheduling, retrospectives, how we do updates, etc.
See Goals
- Observability at Sourcegraph
- Observability developer guide
- Managed instances
- Collecting and inspecting metrics dumps
- How to set up a separate website maintained by Sourcegraph
- How to simulate k8s admin security restrictions
- How to test the Gitlab native integration locally
- How to make updates to global settings and configuration on sourcegraph.com
- Create GCP commitments
- Update various service tokens for sourcegraph.com
- Rollbacks
- We're hiring a Product Manager (apply here) for this role. The engineering team is owning PM responsibilities in the meantime.
- Gonzalo Peci (Engineering Manager) {#distribution-eng}
- Geoffrey Gilmore
- Dave Try
- Dax McDonald
- FQ1 distribution engineer
- FQ2 Robert Lin (early July)
- FQ3 hire
Who is on-call? Slack: /genie whoisoncall Distribution
We have a 24x7 OpsGenie rotation to respond to incidents (events that cause service disruption). You can find more information about being on-call in the handbook.
Incidents on-call
Who is on-call? Slack: /genie whoisoncall distribution-support
You can directly notify the on-call support engineer by using the handle @distribution-support.
We maintain a support rotation to deal day-to-day requests (respond to ad-hoc, time-sensitive questions from customers or other teams, RFC review requests, etc). This makes it easier for other teams to reach out an engineer on the team who's priority is answering these questions and helps other engineers on the team remain focused. You can read more about this on the references below. When you are the active support engineer, your focus and priority is responding to requests and questions in #distributioneers, sometimes this might require creating an issue, re-assigning, looping in other engineers, etc.
If for any reason you are unavailable for a rotation, please coordinate with the team for someone to take over.
References:
There are many reasons to contact the support engineer depending on the priority or urgency of a request. Here are some guidelines that will help ensure we can reply to your request appropriately.
Send us a message in #distributioneers and notify the active engineer by @distribution-support in the message.
Alternatively @distribution-support the engineer in the thread in which he is required.
If this is a time sensitive request, please let us know in the message that this is the case
You can send an urgent notification to the engineer directly from Slack utilizing the following command: /genie alert "ce/p1: Customer XYZ systems are impaired #12345" for distribution-support.
If the engineer is unable, a message will be send to the rest of the team.
Please provide a link to an issue in the message.