Cover Image for Logs, Traces, and Metrics, Oh My! Part 2
Cover Image for Logs, Traces, and Metrics, Oh My! Part 2
Avatar for PHL Code Club
Presented by
PHL Code Club
22 Going
Registration
Welcome! To join the event, please register below.
About Event

A Self Paced Workshop Exploring OpenTelemetry

From the OpenTelemetry docs:

OpenTelemetry, also known as OTel, is a vendor-neutral open source Observability framework for instrumenting, generating, collecting, and exporting telemetry data such as traces, metrics, and logs.

It is a tool set for engineers to gain a deeper understanding of their software as it is running without vendor lock-in.

Why is observability important?

With complex applications comes complex data. It's important to understand the inner workings of your software and how the pieces interact. Being aware of how data flows through your services allows you to pinpoint bugs, bottlenecks and room for improvement.

When things do go wrong (And they will...), having well instrumented software makes debugging and troubleshooting significantly easier.

It allows for both proactive and reactive investigation. Want to better understand what services have high latency and could be better optimized? You can aggregate your traces to get a better look. Need to see why your main API keeps crashing? Look at the logs and check for abnormalities in the resource metrics.

What are we doing?

Participants will be taking an existing set of demo services and setting up an OTel Collector. This workshop will be self guided, you'll work at your own pace as you explore what OTel has to offer.

NOTE: a laptop with Docker installed is required to follow along.

Schedule

  • 6pm

    • Doors open and social time

  • 6:30pm

    • We will sit down and get a really brief introduction to some of the basics of observability and OTel. This will give a baseline for the actual workshop. No prior observability knowledge required.

  • 6:45pm

    • Workshop Time!

    • Feel free to work alone or together, and be sure to ask questions!

  • 8:15pm

    • Closing remarks and a couple final minutes for chatting and socializing

What you need

  • Some way to follow along with the workshop, preferably a computer of some sort.

    • Docker or a similar container runtime is highly recommended. While it is possible to run this without it, that is out of scope so you're on your own then...

  • Some level of coding knowledge or willingness to learn as you go.

  • Curiosity (Super important)

  • Docker or a similar container runtime

What you don't need

  • Prior observability experience

Sponsors

Thanks so much to our generous sponsors!

Resilient Coders

PostHog

YOUR COMPANY HERE

we're always looking for ways to partner with different organizations, if you'd like to support us through sponsorship, shoot us a message > [email protected]

XoXo, PHL Code Club

Location
Indy Hall Clubhouse at 709 N 2nd St
709 N 2nd St 3rd Floor, Philadelphia, PA 19123, USA
Avatar for PHL Code Club
Presented by
PHL Code Club
22 Going