Containerization of microservice based applications enables full team responsibility from code, to operations and eventually maintenance, which enables faster time-to-market, shorter feedback cycles and maximizes continuousness delivery. This modern approach leads to a much higher rate of change, which in turn can lead to chaos. The challenge is how to make sense out of the chaos that deploying containerized microservices at scale creates, and how to get visibility into everything inside, outside and around the containers including the quality of the application’s services.
Join the technical experts from Mesosphere and Instana as they tackle visibility and orchestration requirements to deploy and manage your containerized microservice apps and infrastructure.
4. Architectures Have Evolved
Host Container Middlewar
e
Microservices Business Service
Complexity + Scale Never Cease
Modern Architectures Have Evolved to a
new Level of Distribution and Scale
5. Mesosphere
DC/OS
DC/OS is the Foundation for
Modern Architecture Implementation
• Scheduling
• Container lifecycle management
• Location transparent resource
management
• Continuous deployment
6. DC/OS engineers and automates change
•Containers facilitating rapid
development and deployment
•A container allocation from DC/OS
change code, dependency,
messaging structure
7. Feedback! What just happened!
• What changed?
• Where did change occur?
• Was there any quality impact?
• What is the root cause?
In a system of constant change, operators
need feedback!
19. Challenge with Monitoring Modern Architectures
Host
Middlewar
e
Microservice
Container
Custom Tracing or
APM LoggingContainer monitoringSystem monitoring
• Alerts come from technical silos
• No correlation between alerts and
business services
• Alarms don’t map to problems
• No context of situation
• Sampling/statistical based
monitoring
• Too much specialized expertise
needed to assure quality
No Alignment Between Tools
and the Modern Stack
Business Service
Misalignment = Zero Visibility
20. Instana’s Dynamic APM: Bringing Order to Complexity and Chaos
Host
Container
Middleware
Code Exceptions/Errors
MicroService
Business
Service
Business KPIs &
SLAs
Automatic discovery of architecture with
alignment of context:
• Vertical technical stack
• Service dependency map
• Measurement of service quality
21. Automatic Root Cause Analysis in 3 Seconds
Immediate exact problem
identification with full context
22. Data Ingestion &
Health Calculation
Sensor Data
Real-time Stream
Processing
Incident
Detection
Alerting
Dependency
Health
Metrics
Dynamic Graph
API &
CLI
Configuration
Instana Processing Pipeline
3 seconds from sensing to root cause identification
Quality of
Service
3D Map
23. One Agent
per Host
One Sensor per active
component
Continuous discovery
up the stack
Trace messages
between microservices Sensor Repository
Agent
Knowledge Engine
Elasticsearch
sensor
Tomcat
sensor
JVM sensor
Linux sensor
Auto Discovery
Communication
Local
Sensor Memory
&
Contextual
Compression
Immediate, Automatic and Continuous Discovery of Components and Dependencies
24. Demo Use Cases
Continuous and Automatic Discovery
Application Mapping
Changes Detection and Marathon Events Correlation
Root Cause Understanding