Welcome to Dreamwork

This will be the initial starting point for Dreamwork documentation. It will start out as a bunch of links, miscellaneous ramblings and general dumping ground for thoughts as we start to put this together.

As I was stumbling along, I found that we have a lot of the info already in github. https://github.com/Banno/dreamwork The things than non-engineers should know about should get pulled that into this page or at least have mentions and links. We have some stuff in Knowledge

Team Charter

Who we are

Team members can be found in the team information in GitHub

What We Do

Domains

Dreamwork is responsible for the domains listed in the Domain Ownership By Teams document.

Scaling

The Scaling Spreadsheet needs to get updated every two weeks. We want to make sure that our services are scaled correctly to handle usage spikes that normally occur at the end of the month.

The pertinent values can be monitored using the CPU/Memory Utilization dashboard in Prometheus.

Tools Used

Slack

Most of our communication happens in Slack. There are lots of channels about various hobbies for you to check out. For the Dreamwork team, we have the following channels that you’ll want to join.

• General communication

  • #org-dreamwork - Our public page for general questions
  • #team-dreamwork - This the team channel where our team chats about what they are doing. We also list our PR reviews here. Go give it a review and +1.

• Automated messages

  • #alerts-dreamwork-production - Alerts generated in production systems
  • #alerts-dreamwork-uat-staging - Alerts generated in UAT and staging systems
  • #auto-dreamwork-ci - Messages from Jenkins
  • #auto-dreamwork - Additional automated messages, primarily from Jira

Jira

This is where we keep track of the work we are doing and things we want to do in the future.

• Kanban Board - The current stuff we are doing
• Roadmap - Shows what we are planning on working on

Jenkins

Jenkins is an open-source automation server that builds and deploys our services to the different environments we use. (Staging, UAT, and Production)

A majority of your interaction with Jenkins will be approving builds and sending out release-notes, all of which can be monitored and interacted with from our #auto-dreamwork-ci slack channel.

Kibana

Kibana is an interface that gives us the ability to search, view, and visualize a massive amount of logs from our services and use that information to diagnose issues/bugs.

Feel free to experiment with filtering and see all the different kinds of information we have to sort through here

Grafana

How do we know our services are running smoothly? We have a couple of useful Grapha graphs you’ll want to check out.

Rates, Timers, Guauges, etc are found here.

Dashboard of Memory and CPU are here

Alerting

• Are we getting alerts before things go up in a ball of flames? We’re using PagerDuty to alert people off-hours.
• You can also page the Dreamwork Firefighter on Slack by typing /pd-dreamwork Help, my cat is stuck in the tree! OK, don’t sent that exact message because we won’t be able to help, but you get the idea.

Meetings

We have retrospective meetings every two weeks. You can find the notes here

Really helpful links

Need an account setup? Create a service ticket here: https://banno-jha.atlassian.net/servicedesk/customer/portals Tech Ops -> Account Request. You can also try their slack channel #org-tech-ops