In this session, Melissa Sussman, Lead Technical Evangelist at Sumo Logic, explores the company's contributions to open source projects. Sumo has made a serious commitment to OpenTelemetry (OTel), OpenSLO, and open core solutions. Melissa also discusses data collection and how open source tooling (such as Kubernetes, Prometheus, Fluentbit, and Fluentd) are used with Sumo Logic products. Speakers: Melissa Sussmann

1. Sumo Logic Confidential
Sumo Logic <3
Open Source
Melissa Sussmann, Lead Technical Advocate

2. About me
• Lead Technical Advocate at Sumo Logic
• 11+ years of domain expertise and
experience as an engineer, product
manager, and product marketing
manager for developer tools.
• Love gardening, reading, playing with
Mary Lou (see Milou on right), and
working on side projects.
• Some past projects include: running
nodes on the lightning network, writing
smart contracts, running game servers,
building dev kits, sewing, and
woodworking
LinkedIn: https://www.linkedin.com/in/melissa-sussmann-9b446076

3. Sumo Logic <3 Open Source
Open Analytics Beta *
Bring Your Own Analytics (BYOA) and models to process your data
your way on the Sumo Logic platform.
Feb 2022
Sumo Logic Distro for OpenTelemetry
Sumo Logic established OpenTelemetry as its future standard to
collect all machine data, breaking from the legacy model of using
proprietary agents to gather critical application and infrastructure
telemetry.
April 2022
SLOGen becomes part of OpenSLO Standard
In addition to direct contributions to the OpenSLO specification,
Sumo Logic has contributed a new sub-project into OpenSLO called
slogen. This open source tool takes OpenSLO-formatted YAML files
to automate infrastructure configuration.
May 2022
Sensu Catalog
Self-service infrastructure monitoring, powered by an open
marketplace – the Sensu Integration Catalog. Backed by Sensu’s
industry-leading monitoring as code solution, the Sensu Integration
Catalog enables real-time
April 2022

4. Sumo Logic confidential
Logs
Events
Metrics
K8s Data Collection With Sumo (OSS)
Collection
Prometheus
Fluent Bit
Fluentd
Enrichment
Fluentd
Pod & Pod Labels
Namespace &
Namespace Labels
Node
Cluster
Service
Deployment
Container
Storage &
Data Access
Traces

5. Sumo Logic confidential

6. Sumo Logic confidential
Why do I need Service Level Objectives (SLO)?
“Services that we design and build must have a
set of requirements about their runtime
characteristics. This is often referred to as a
Service-Level-Agreement (SLA). SLAs include
remedies, impacts, and much more…So, we
will focus on the term Service-Level Objectve
(SLO). SLOs are commitments by the
architects and operators that guide the design
and operations of the system to meet those
commitments.” - Database Reliability
Management, Laine Campbell + Charity Majors

7. + SLOgen

8. Microlesson: Enabling OpenSLO with SLOgen
To the left, we have a microlession
teaching you how to enable OpenSLO
with Sumo Logic’s SLOgen.
Learn more about the OpenSLO
specification here:
https://github.com/OpenSLO/OpenSLO
Check out the project here:
https://github.com/OpenSLO/slogen

9. Sumo Logic confidential
• In-app marketplace
• Self-service monitoring
• Turn-key integrations
• Real-time deployment
• Monitoring as code
• Open marketplace
What is the Sensu Catalog?

10. 10
Real-time deployment of
monitoring integrations
Prompt users for relevant
configuration
Self-service infrastructure monitoring
Learn more @ https://github.com/sensu/catalog

11. Sumo Logic confidential
Sensu Catalog – Intro Webinar & Demo(s)
https://github.com/sensu/catalog

12. Sumo Logic confidential
Why “unified collection + analytics” matters

13. Data Collection for Protection and Privacy
Disparate backends are required
to protect personally identifiable
data due to compliance standards
(GDPR, COPPA, CCPR)
Presents challenges for data
collection, particularly without the
use of a common, vendor-agnostic
open standard.
“The wonderful thing about standards is that
there are so many of them to choose from.”
Grace Murray Hopper, Naval Officer and computer
pioneer, 1906-1992

14. Data Collection via Telemetry Pipelines
Telemetry pipeline: routes
data (logs/metrics/traces) from
where it is generated to its
corresponding backend.
Open Telemetry: an open
standard (from the CNCF) that
aims to unify “receivers” in a
telemetry pipeline.
Receiver
Takes the data in at the start of a telemetry pipeline.
Can be in the form of logs, metrics, traces, etc.
Buffer
Holds the data for a short period of time until the
processors or exporters are ready to take in the data.
Happens mostly in the processor or exporter.
Exporter
The end of the telemetry pipeline. This is where the data
gets exported to its corresponding back-end in this pipeline.
Processor
Analyzes or transforms the data from a buffer.

15. Quick History on OTel
OpenCensus:
● metrics and tracing focused
● originated at Google, based on Census concepts
● Omnition started incorporating it into a
complete observability solution
OpenTracing:
● distributed-tracing focused
● originated at Google, based on Dapper concepts
● CNCF project since 2016
● API used by many vendors (Jaeger, DataDog,
etc.)
OpenTelemetry:
● merge of OpenCensus + OpenTracing
● announced May 2019
● backed by all major vendors
● CNCF project (incubating since Aug 2021)

16. OpenTelemetry users build and own
their collection strategies,
without vendor lock-in.
OpenTelemetry puts the focus on
analytics not collection.
OpenTelemetry is
core to Sumo’s collection strategy.
Why OpenTelemetry matters for Sumo Logic

17. Thanks for joining!
Reach out to sales@sumologic.com
Start your free trial: https://sumologic.com/sign-up