Team Pupper

Welcome to Pupper

This will be the initial starting point for Pupper 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.

For more information visit us in Confluence here

This should be a living document. If you run into something that you don’t know how to do, it’s probably a good idea to list it here with the solution you find. It’s a good bet that someone else is going to have the same issue at some point and it would be nice to leave them a breadcrumb trail to follow.

Things will get moved around and pushed into other folders and such. Everyone hates broken links. If you move a document around, make sure you update the links in this doc. Before you say anything, I know this doc can use some better formatting. Feel free to spruce it up.

Team Charter

Who is Pupper and what are we responsible for.

Capybara

Marmot

What We Do

Services

Pupper is responsible for the following services. Here is where you’ll find our main Github.

Capybara

  • Alerts Enhancement Alert Settings
  • Card Alerts
  • EES ingress/egress
  • Institution Images
  • Institution Notes
  • Login Secrets
  • Member-to-Member Transfers
  • Mobile Billing
  • Notifications (Push, Email, SMS)
  • Reports
  • symXchange
  • symXchange Proxy Service
  • Zelle
  • ToTP Service

Marmot

  • Banno UIS Configuration Service
  • Banno Users
  • Consumer Contact Info
  • Consumer External Links
  • Consumer User Search
  • Consumers
  • core-login-registration
  • Mobile Admin
  • user-sync
  • View Employee Info

Pupper is in the process of merging in the following services from Capybara Here is where you’ll find our main Github.

Scaling Spreadsheet - This 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.

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 Pupper teams, we have the following channels that you’ll want to join. If it’s a private channel, just ask someone and we’ll get you in.

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

  • Customer Support Issues - Support will create OPS tickets through their help desk software. We have limited licenses for that so ETRIAGE tickets get created. Every team needs to look at these tickets and determine if they are responsible for fixing the issue. PUP tickets get created to keep track of any action we are doing to resolve the customer issue. This is a list of the ETRIAGE tickets that need our attention.

  • Customer Issues - You start working on a ticket and find out there isn’t enough information or it looks like a problem on the customers side. How do you get in contact with the customer or who should you talk to?

    Need to add stuff here explaining what to do.

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-curry 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.

Services, JVM, Postgres and such are found here.

Dashboard of Memory and CPU are here

Pupper will be merging in these services Rates, Timers, Guauges, etc are found here.

Dashboard for Kafka 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 Pupper Firefighter on Slack by typing /pd-puper 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.

Runbooks

Bad things will happen and we need to put out the fire. It might be the middle of the night, you just got page and need to resolve a problem. You’ve come to the right place. You’ll find our Runbooks on how to resolve issues, find important logs, or a list of people who can help.

Meetings

We do a lot of meetings. We should keep track of meeting notes and action items. Yeah, this is an area of improvement.

Onboarding

Whether you are new to JHA or the team, there is a lot to learn. Here are some useful things to know.

  • You may have already gone through the main Onboarding doc. If not, that’s a good place to start. Have you seen the company wiki? How about the one for Data Services? Be carefully so you don’t get into an endless loop on these pages.

  • There is a lot of information out there. Guess what? It can always use a little love. Here is the source for the wiki and how you can help keep it updated.

  • If you’re on the Pupper team, you should have access to our Team Folder. We’re still in the process of cleaning it up, but there is still some good stuff out there.

  • Learn to log into the Banno platform on any of our test institutions in production. Play around with the app to become familiar. A good starting point is the Test Creds page. Feel free to jump in and look around, but please don’t update things yet since we do demos and such over there.


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

Education links from the Product Manager section How Core Works - part 1 How Core Works - part 2