DevOps includes the broadest range of applied IT topics. Everyone's experience matters, from a startup, to a struggling IT department, to the likes of Google and Netflix. We share experiences from beginners and masters alike. Presentations can be aspirational, a post-mortem, and everything in between.
BE CONSIDERATE TO YOUR ORGANIZER AND SPONSORS BY UPDATING YOUR RSVP STATUS
Being a 'No show' or holding spots until the last minute then not attending is not only rude, but impacts the ability for other members (that can commit to attending) from coming if there is a limit. If this happens repeatedly it could lead to removal from the group.
Good RSVP/attendance etiquette · It is courteous to accept or decline an invitation within a few days of receiving it. This helps with event planning and provides valuable feedback to the organizers. · You should update your RSVP as soon as your plans change. If that's within 24 hours of the event, you should also contact the organizer personally via email (contact link under organizers photo) or phone. · If you RSVPed 'Yes', you show up to the event. If you can't show up, change your RSVP accordingly and explain to the Organizer why you couldn't attend. · If you RSVPed 'No', you should not attend the event, unless you change your RSVP to 'Yes' if space allows. · If you RSVPed 'Maybe', you are required to change your RSVP to 'Yes' or 'No' at least 4 days before the event. You should change your 'Maybe' to a 'No' as soon as possible in the event you are not able to attend so that others may plan to go.
Note: Maybe's may be changed by the organizer to a 'No' to make room for others to attend.
When xMatters moved from its own data centers to a public cloud platform (GCP), it came with some amazing opportunities to optimize code, speed up deployment processes, downsize infrastructure, and even to evaluate new monitoring system options. The adoption of Prometheus represented represented a significant change compared to the company’s existing solution— from a limited “trinary” signal to the ability to use time-based monitoring parameters to drive business-specific use cases.
In this session, xMatters will detail how it used Prometheus to deliver high availability services with multiple instances, focusing on the following implementation components that are noteworthy for any organization:
· Service Discovery: Use Hashicorp Consul to discover services such as Rabbitmq and be aware of important caveats that come with using Consul tags (ie checking for health of Kubernetes pods that comprise core services)
· Magic Math: Tie-in the statistics that matter to your business with Promotheus’ alterting rules. For example, Prometheus expressions allow you to track key uptime SLA’s and notify team members when they’re at risk.
· Analysis paralysis: With great power comes great responsibility. Prioritize the metrics you track across your team. When you’re tracking several systems, be prepared for svcprom to be more heavily loaded — which means you need to give it more resources — and you need to prepare your pod health checks for a possibly slow startup/render time
6:10-7:00: Presentation: Curtis St. Pierre, DevOps Engineer, xMatters.com