Why 'Log Analytics' matters?
Competition
ROI & Use Cases
AWS
100
"Sometimes it feels less like looking for a needle in a haystack, and more like looking for a needle in a needle stack."
Elaborate on what this quote is referring to...
Troubleshooting, monitoring - speaks to challenge of always being on alert
100
Name 1 of the 3 'on-prem' solutions / vendors that we compete with for Log Analytics
Splunk Enterprise, ManageEngine, Mezmo
100
“We used CloudWatch, CloudTrail, as well as some other tools… Sumo [Logic] brings everything together and makes life easy.”
Which persona(s) would be most likely to say something like this? (EB or Practictioner)
Practitioner
100
What is 'APN' and why does it matter?
- The AWS Partner Network (APN) is a global community of partners that leverage programs, expertise, and resources to build, market, and sell customer offerings. This diverse network features 100,000 partners from more than 150 countries.
- "Once we joined the APN, we not only got the technical endorsement to promote our platform, but also increased visibility to potential customers and access to programs and resources to build GTM strategies that opened new regions and verticals. By leaning into AWS and the APN, Sumo Logic went from a small startup to a global SaaS company." - Anselmo
200
Name 3 ways that 'Log Analytics' helps with AWS troubleshooting
Monitoring the performance of business-critical applications
Monitoring the health of the infrastructure running applications
Quickly troubleshooting issues and reducing MTTR by efficiently analyzing all pertinent log data
Finding the root cause faster by filtering the noise to focus on the right signals
Better manage the user experience by tracking operational objectives with SLIs and SLOs
Reducing number of observability tools
200
Humio and Grafana Loki are examples of 'Non-indexing Solutions'...what are the main differentiators to highlight vs. Sumo's centralized solution? (Hint: think about it in terms of data tiering, real-time analytics, ad hoc analytics, retention, and enterprise class)
Data Tiering / Indexing:
- Not available! All data gets ingested, but not indexed for future use (i.e. dashboarding)
Real-time Analytics:
- 'Sort of'. Slow performance for large queries due to last minute indexing
Retention:
- Yes, but difficult to configure retention period for different data sets
Enterprise Class:
- Lacks RBAC granularity, visibility to manage data sprawl
200
Based on our "Survey Spotlight", how did Sumo Logic impact organizations?
___ % consolidated tools
___ % saw improved troubleshooting, cutting MTTI/MTTR
___ % fostered greater collaboration among different teams (DevOps, IT, Product, etc...)
82% consolidated tools
68% saw improved troubleshooting, cutting MTTI/MTTR
64% fostered greater collaboration among different teams (DevOps, IT, Product, etc...)
200
What is the median amount of AWS 'services' used by our Sumo customers?
26
*why is this important to know?
300
Log Analytics comes in many shapes in sizes...for this reason, we believe a __________ SaaS solution can deliver the best results.
centralized
"Before Sumo Logic, a dedicated development resource would go through all the logs and uncover issues. Now, with just a single Sumo Logic query, the development team can identify exactly which tenant in the multi-tenant architecture or which database query is causing issues"
300
What are some of the key disadvantages of an 'on-prem' solution? (Hint: think about it in terms of data tiering, real-time analytics, ad hoc analytics, retention, and enterprise class)
Data Tiering / Indexing:
- 'Sort of'. Data not ingested or indexed until pulled out of cold storage.
Ad Hoc Analytics:
- Not possible. Archived data requires 're-hydrating' for analysis
Retention:
- $$$! Hope your cost per GB is low!
Enterprise Class:
- Requires work. Time and effort to manage and maintain is high.
300
"Sumo Logic transformed what was a manual, __-hour log analysis effort down to a single query, so we can immediately identify any issues with product performance. Empowered with the insights from Sumo Logic, we’ve gained a __-fold performance increase in speed for customer database queries.”
16-hour; ten-fold
- Sudhaker Gorti, Co-founder & CPO, LeadSquared
300
Which Sumo Logic employee specializes in the AWS + Sumo Logic alliance? (DAILY DOUBLE)
Anselmo Barrero (Sr. Director, Strategic Partner Sales)
400
What are some common challenges with Log Analytics? (Hint: think broadly about how data is managed)
- Difficult to collect & parse log data from a variety of sources
- Difficult to identify and correlate log events
- Difficult to store & analyze large volumes of data
- Difficult to keep up with ever-increasing volume and variety of log data
- Difficult to secure log data and prevent unauthorized access
- Difficult to get the right people, the right information, at the right time!
400
These two companies / vendors fall under the "Distributed Analytics" category. Who are they?
Datadog & Coralogix
"A distributed analytics solution is a system where log data is collected and analyzed at the source, or near the source."
"A centralized log analytics solution is a system where log data is collected from all sources and stored in a central location. This can help to improve visibility and compliance, as all data is stored in a single place. Centralized log analytics solutions can also be more cost-effective, as they can be used to consolidate multiple data sources."
400
“We used CloudWatch, CloudTrail, as well as some other tools… Sumo [Logic] brings everything together and makes life easy.”
What do Cloudwatch and CloudTrail do respectively?
- AWS CloudWatch is a monitoring service that collects and stores metrics, logs, and events from AWS resources and applications. It can be used to monitor the performance of applications, identify trends, and troubleshoot problems.
- AWS CloudTrail is a monitoring service that records AWS API calls made by users, roles, or services. It can be used to audit AWS activity, troubleshoot problems, and comply with regulations.
400
"But wait...doesn't AWS already offer monitoring and logging?"
What are some ways you could respond?
Yes, but this is not their primary focus like us
More limited logging capabilities vs. LogReduce/LogCompare
Sumo can centralize AWS data alongside data from other clouds/other tools
Sumo can also provide complete observability across telemetry types
500
Explain to me how the OpenTelemetry framework relates to Sumo Logic's Log Analytics solution. (Hint: what is a big common thread / theme that applies to both?)
- "OpenTelemetry is an open source observability framework that makes it easy to collect and export telemetry data (metrics, logs, and traces) from applications and services. Log analytics is a process of collecting, storing, and analyzing log data to gain insights into the performance and health of applications and systems."
OpenTelemetry can be used to improve the efficiency and effectiveness of log analytics by:
- Standardizing the way telemetry data is collected and exported, which makes it easier to integrate with different log analytics solutions.
- Providing a unified view of telemetry data from different applications and services, which makes it easier to identify and troubleshoot problems.
- Enabling the use of advanced analytics techniques to gain deeper insights into the performance and health of applications and systems.
Extra: Why do you think we ask customers if they have adopted OT?
500
What are the pitfalls of "Distributed Analytics" solutions? (Hint: think about it in terms of data tiering, real-time analytics, ad hoc analytics, retention, and enterprise class)
Data Tiering / Indexing:
- Meh. Requres storing data off-site and 're-hydrating' when needed
Ad Hoc Analytics:
- Not really. Dashboards and queries can't be run on un-indexed data.
Retention:
- No. Requires use of (possible insecure) off-site storage
Enterprise Class:
- Nope. Is data moved to a customer's S3 bucket still 'secure'?
500
The AWS use case presents a 'natural place to land' for Sumo Logic. We see this validated in our customer infrastructure data, which shows the following breakdown across our customers. Match each infrastructure with the correct statistic / adoption rate.
Stats: 1%, 15%, 18%, 8%, 59%
Infrastructures: Multi-cloud, On-prem /Other Cloud, Azure Only, AWS Only, GCP Only
500
What is this image showing at a high level? (Hint: what do the colors / blocks represent?)
Unified visibility across accounts, regions and services
40+ out-of-the-box dashboards and alerts from CloudTrail/ CloudWatch logs, CloudWatch and EC2 metrics
Dozen+ AWS services