BEGIN:VCALENDAR VERSION:2.0 PRODID:-//Pentabarf//Schedule 0.3//EN CALSCALE:GREGORIAN METHOD:PUBLISH X-WR-CALDESC;VALUE=TEXT:Monitoring and Observability devroom X-WR-CALNAME;VALUE=TEXT:Monitoring and Observability devroom X-WR-TIMEZONE;VALUE=TEXT:Europe/Brussels BEGIN:VEVENT METHOD:PUBLISH UID:13551@FOSDEM22@fosdem.org TZID:Europe-Brussels DTSTART:20220206T100000 DTEND:20220206T101000 SUMMARY:Monitoring and Observability devroom: Opening DESCRIPTION:
Opening!
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Monitoring and Observability URL:https:/fosdem.org/2022/schedule/2022/schedule/event/moniobserv2022open/ LOCATION:D.monitoring ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Richard Hartmann":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:12803@FOSDEM22@fosdem.org TZID:Europe-Brussels DTSTART:20220206T101000 DTEND:20220206T105000 SUMMARY:Adopting OpenTelemetry and its collector DESCRIPTION:In this session, we’ll see why we adopted OpenTelemetry & its collector for an internal platform at Ubisoft - to collect/process/export all our logs, metrics, and traces.We’ll explain how we handled the required mindset change: why people should instrument more their code, and how to onboard them.And of course, we’ll talk about the benefits of fully adopting OpenTelemetry.
The intended audience is people who want to adopt OpenTelemetry, or who are already using part of it - for example the SDK for tracing - and are considering a full switch.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Monitoring and Observability URL:https:/fosdem.org/2022/schedule/2022/schedule/event/adapting_otel/ LOCATION:D.monitoring ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Vincent Behar":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:12400@FOSDEM22@fosdem.org TZID:Europe-Brussels DTSTART:20220206T105000 DTEND:20220206T113000 SUMMARY:Bootstrapping a multi dc cloud native observability stack DESCRIPTION:A gentle introduction to Observability and how to setup a highly available monitoring platform across multiple datacenters.
During this talk we will investigate how we can setup and monitor an monitoring setup across 2 DCs using Prometheus, Loki, Tempo, Alertmanager and Grafana. monitoring some services with some lessons learned along the way.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Monitoring and Observability URL:https:/fosdem.org/2022/schedule/2022/schedule/event/multi_dc_cloud_native_observability/ LOCATION:D.monitoring ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Bram Vogelaar":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:12768@FOSDEM22@fosdem.org TZID:Europe-Brussels DTSTART:20220206T113000 DTEND:20220206T121000 SUMMARY:Introduction to Continuous Profiling using Pyroscope DESCRIPTION:Profiling is an effective way of understanding which parts of your application are consuming the most resources. Traditionally, logs, metrics and traces have been considered the three pillars of observability, but more recently profiling has emerged as a fourth pillar to be used alongside these other observability tools.
Continuous Profiling, in particular, adds a dimension of time that allows you to understand your system’s resource usage (i.e. CPU, Memory, etc.) over time and gives you the ability to locate, debug, and fix issues related to performance.
In this talk, we'll present Pyroscope, an Open Source Continuous Profiling platform, explain the particular challenges it needs to tackle and showcase how it can be used to analyze and fix performance bottlenecks:
In this session, we’ll see eBPF monitoring in action applied to the Kafka world as an example of a complex Java application: identify Kafka consumers, producers, and brokers, see how they interact with each other and how many resources they consume. We'll even show how to measure consumer lag without external components. If you want to know what’s next in Java and Kafka observability in Kubernetes, this session is for you.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Monitoring and Observability URL:https:/fosdem.org/2022/schedule/2022/schedule/event/monitoring_kafka_using_ebpf/ LOCATION:D.monitoring ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Anton Rodriguez":invalid:nomail ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Ruizhe Cheng":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:13214@FOSDEM22@fosdem.org TZID:Europe-Brussels DTSTART:20220206T134000 DTEND:20220206T142000 SUMMARY:Periskop: Exception Monitoring at Scale DESCRIPTION:This talk is aimed for engineers operating in distributed environments (or microservices) interested in monitoring exceptions at scale. We introduce the open source project "Periskop", a pull-based exception monitoring service built at SoundCloud and inspired by Prometheus.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Monitoring and Observability URL:https:/fosdem.org/2022/schedule/2022/schedule/event/periskop/ LOCATION:D.monitoring ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Jorge Creixell":invalid:nomail ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Marc Tuduri":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:13524@FOSDEM22@fosdem.org TZID:Europe-Brussels DTSTART:20220206T142000 DTEND:20220206T150000 SUMMARY:Profiling in the cloud-native era DESCRIPTION:Continuous profiling is a widely used practice at Google but has only recently started gaining popularity in the Observability space, however, resources on this topic are still rare compared to other observability signals especially on open source projects.This talk intends to educate the wider community about the possibilities of continuous profiling, and give a glimpse into open-source tooling allowing everyone to join in on the practice and enabling everyone to build better software.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Monitoring and Observability URL:https:/fosdem.org/2022/schedule/2022/schedule/event/cloud_native_profiling/ LOCATION:D.monitoring ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Matthias Loibl":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:12900@FOSDEM22@fosdem.org TZID:Europe-Brussels DTSTART:20220206T154000 DTEND:20220206T162000 SUMMARY:Unikraft Performance Monitoring with Prometheus DESCRIPTION:Unikraft, and similar unikernels, offer isolation by running a single application inside a separated virtual machine. As such, extracting information from the machine can prove difficult. Moreover, because Unikraft offers support for running a single process at a time, alternate solutions had to be found for exporting data. Prometheus is a common tool used to collect and visualize data that offers decoupling from the observed system, as such, we saw it as a prime candidate for exporting information.
Our solution was to port a Prometheus exporter inside Unikraft as a separate library and run it on a separate thread. Information from the unikernel is extracted by Prometheus through an intermediary library, named ukstore, that behaves like a simplified ProcFS. ukstore offers an easy method for accessing information and metrics from the system. Using Prometheus with Unikraft, we are thus able to extract performance metrics from highly-specialized virtual machines, store them in a time series database and display them using plots.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Monitoring and Observability URL:https:/fosdem.org/2022/schedule/2022/schedule/event/unikraft/ LOCATION:D.monitoring ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Cezar Craciunoiu":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:12740@FOSDEM22@fosdem.org TZID:Europe-Brussels DTSTART:20220206T162000 DTEND:20220206T170000 SUMMARY:What More Can I Learn From My OpenTelemetry Traces? DESCRIPTION:Of the three observability data types supported by OpenTelemetry (metrics, logs, and traces) the latter is the one with most potential. Tracing gives users insights into how requests are processed by microservices in a modern, cloud-native architecture.
Jaeger and Grafana can visualize a single trace, showing how an individual request traversed your entire system. This helps for distributed debugging and analysis, but using traces only this way is limiting.
What if you stored tracing data in a SQL database? You could ask global questions about your system. You could find slow communication paths, where the error rate spiked since the last deployment, or where the request rate suddenly dropped. Thus, tracing can be used proactively to help you spot issues before your customers do.
This talk will show you how to do all the above by ingesting OpenTelemetry traces into a PostgreSQL/TimescaleDB database, and building custom dashboards using SQL to make the most out of your tracing data.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:Monitoring and Observability URL:https:/fosdem.org/2022/schedule/2022/schedule/event/learn_from_otel_traces/ LOCATION:D.monitoring ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="John Pruitt":invalid:nomail END:VEVENT END:VCALENDAR