On average, a business supporting digital transactions now crosses 35 backend systems—and legacy tools haven’t been able to keep up. This session will cover how MuleSoft uses InfluxCloud to help power their monitoring and diagnostic solutions as well as provide end-to-end actionable visibility to APIs and integrations to help customers identify and resolve issues quickly.

1. MuleSoft & InfluxData
Anypoint Monitoring
From better visibility to business impact
Gagan Kanwar
Partnerships @ MuleSoft

2. MuleSoft 101

3. Financial Services and Insurance Retail and Consumer Goods High Tech
Healthcare Education and Public Sector Manufacturing
Trusted by 1,500+ customers across industries

4. TAKING AN API-LED APPROACH TO
UNLOCK DATA FOR CUSTOMERS,
EMPLOYEES AND PARTNERS
“With MuleSoft, Airbus is
completely rethinking how it builds
applications. We are moving to
composable building blocks,
microservices and APIs. It's about
developing faster and cheaper,
and at scale.”
- Chris Taylor, VP of Digital Accelerator
4
Delivering projects 4x faster
• Built a library of reusable APIs which
aggregate data from multiple backend
systems allowing the team to develop 3
mobile apps in 2 months
Millions of € in value delivered
• Reusing APIs and core assets to save time
and money; better adherence to
compliance for cost avoidance
Rapidly connecting legacy
systems to cloud applications
• Unlocking data from cloud and
on-premise systems – including multiple
SAP systems like SAP S/4 HANA and
Skywise, a customer big data platform –
to create mobile apps to streamline
manufacturing processes

5. How customers actually use MuleSoft

6. Using APIs to drive simplicity & consistency

7. The API-Led Connectivity Approach
Customers
Web app API
OrdersSalesforce
customers
SAP
customers
Inventory &
ATP
Oracle ERP AS400 Data
Warehouse
Order
status
Order
history
Mobile API
System
Process
Process
Experience

8. Enterprise systems have grown enormously complex
A single web or mobile transaction crosses an
average of 35 different systems or components
Complexity introduces:
1. Gaps in observability
2. Increased time to identification
3. Increased time to resolution
4. Poor customer experience
5. Lost revenue, etc.

9. Solution Driver → Monitor the Application Network
A largish customer looks like this:
● 2017 Total # of API Calls: 9 Billion
● Average # Transactions/Second: 275
● Y/Y Transactions Growth Rate: ~ 30%
● Tracking to 12 Billion Transactions (2018)
● Very Large Customers → Stringent SLAs
● High Product Usage & Data Volumes
● High & Unpredictable Cardinality
● Compex Heterogeneous Environments
○ Public Cloud, Private Cloud & Gov Cloud
○ Hybrid
○ Completely On-Prem

10. What we wanted in a data infrastructure product/partner
1. Does it natively manage time-series data
a. Core use case is Enterprise Monitoring → Highly Temporal
2. Can it deal with very high cardinality data sets
a. API calls have well-defined formats
b. But some fields (e.g. IP) can very quickly drive up cardinality
3. Does it supports cloud, hybrid and fully on-prem environments
4. Can we deploy in both Multi-Tenant & Single Tenant
a. Business model optionality
5. Can we get to a very specific per-metric price range
a. We are a public company - need to tightly manage COGS
6. Can we host the solution in our own AWS instance
a. Data residency requirement, access controls, etc.

11. Decision parameters & process
1. Business Case (define business objectives, save or make money, target market, customer demand)
2. Product (does the product do what we need, will it fit in with our broader infrastructure)
3. Roadmap (thought leadership, are we going in the same direction e.g. GovCloud)
4. POC to validate scalability (address scale & latency needs, internal stakeholder alignment)
5. Competitive Evaluation (who else could do this, e.g. SignalFX, DataDog, CloudWatch)
6. Unit Economics & Deal Structure (meet COGS requirement, economic alignment, creative thinking)
7. The Team (technical chops, ongoing product support, exec alignment)
8. Customer References (will they deliver, is the service getting better, product downtime)
9. Legal (we planned to OEM, not just license - extra legal & commercial complexity)
10. Confidence (Strategic Deal - High Risk & High Reward)

12. Anypoint Monitoring 101
End-to-end actionable
visibility for APIs and
integrations:
● 360-degree functional APM
(Application Performance Monitoring)
● Two Product Flavors:
○ Included (Multi-Tenant)
○ Premium (Single-Tenant)
● Log Management
● Integrated Visibility
● Advanced Alerting

13. Reducing MTTR

14. Reducing MTTR

15. Reducing MTTR

16. Reducing MTTR

17. Protecting PII and sensitive log data

18. Warehousing logs for auditing, compliance and security