Part of Elastic - 138 groups

Elastic Seattle User Group

4.7•93 ratings

Seattle, WA, US

1,605 members · Public group

What we’re about

We’re delighted to have you join the Elastic global community! This group is for anyone interested in making data usable in real-time and at scale for use cases like security, observability, enterprise search, and many more, using our Elasticsearch, Kibana, Logstash, and Beats products (https://www.elastic.co/products/).

Speak at a meetup: The Community wants to hear from you! Present about your Elastic Stack stories, be it a 5-15 minute lightning talk or a detailed 25-45 minute technical presentation with Q&A. Our Speaker Guide is full of tips on giving a stellar presentation. If you’re interested, visit the elastic/call-for-meetups repo or send us an email at meetups@elastic.co.

Elastic Community Youtube Channel: All meetups are recorded and uploaded to YouTube within a few days of the event. Subscribe here to stay up to date!

Local community organizers wanted!

We’re always on the lookout for committed local organizers who will help the group thrive. If this sounds interesting to you, the Community Team at Elastic is here to support you! Email us at meetups@elastic.co.

We know that people enjoy giving back to the communities they care about, so we’ve created an Organizer guide to help you get started on your path to leading an Elastic user group.

Learn more about Elastic:

Elastic Contributor Program: https://www.elastic.co/community/contributor

Elastic Community: https://www.elastic.co/community

Community Newsletter: https://www.elastic.co/community/newsletter

Discussion Forums: https://discuss.elastic.co/

Elastic Cloud Free Trial: https://www.elastic.co/cloud/elasticsearch-service/signup

Code of Conduct: This Meetup community adheres to the Elastic Community Code of Conduct. Attendance to events run as part of this Meetup group means you agree to be an awesome human and engage by these rules.

Upcoming events

See all

Observability and SLOs with Elastic
Thu, Jan 29 · 5:30 PM PST
SURF Incubator, 999 3rd Ave SUITE 700, Seattle, WA, US
Join the Elastic Seattle User Group on Thursday, January 29th for an exciting meetup.

We’ll feature presentations from Justin Castilla (Sr. Developer Advocate at Elastic) and Rajesh Sharma, followed by networking, refreshments, and pizza with the Seattle tech and Elastic community.

📅Date and Time:
Thursday, January 29th from 5:30-7:30 pm PST

📍Location:
999 3rd Ave SUITE 700, Seattle, WA 98104 - We'll be in the Sunset Beach room

🚗 Parking:
- Book a spot on SpotHero
🪧 Arrival Instructions:
Upon arrival at 999 3rd Ave, head to the Surf Incubator on floor 7. The meetup will take place in the Sunset Beach room.

Please note: The building locks after 6pm -
The building locks for individuals who park outside of the onsite garage after 6pm, so we recommend arriving at the meetup start time of 5:30 or using the onsite garage if you are running late.

If you park in the onsite garage, attendees can access floor 7 with no restrictions after 6pm.

📝 Agenda:
- 5:30 pm: Doors open; say hi and eat some food
- 6:00 pm: Observability and SLOs with Elastic Rajesh Sharma
- 6:30 pm: Talk # 2 - Details coming soon- Justin Castilla (Sr. Developer Advocate at Elastic)
- 7:30 pm: Event ends
💭 Talk Abstracts:
Observability and SLOs with Elastic - Rajesh Sharma

This session will show how to move from “we have metrics/logs/traces” to reliable, measurable user experience by defining and operating Service Level Objectives (SLOs) in the Elastic Stack. We’ll cover how to translate business expectations into SLI/SLO definitions, instrument services with Elastic Observability (APM, logs, metrics, synthetics), and use Kibana to track error budgets and detect fast-burning reliability issues before they become incidents. Attendees will leave with practical patterns for choosing meaningful SLIs, setting realistic targets, and wiring burn-rate alerting and dashboards that align engineers and stakeholders around outcomes.

Key takeaways:
- SLO fundamentals: SLIs, targets, and error budgets (what to measure and why)
- End-to-end observability: correlating APM + logs + metrics + synthetics to explain SLO misses
- Operationalizing reliability: error-budget reporting, burn-rate alerting, and actionable runbooks in Kibana
- Adoption patterns: starting small, iterating targets, and avoiding vanity metrics

Demo: “Checkout API SLO in 10 minutes”
A small “Checkout” HTTP endpoint (e.g., POST /checkout) instrumented with Elastic APM, plus a synthetic test that runs the checkout flow every minute.
3 attendees