Visibility into your infrastructure is critical, and the Elastic (ELK) Stack, brings its logging strengths to your metrics use case. Discover how simplified data onboarding with hundreds of prebuilt integrations, automated insights with alerting and machine learning, and new visual tools built for exploring infrastructure metrics are streamlining the monitoring use case.
08448380779 Call Girls In Civil Lines Women Seeking Men
Why you should use Elastic for Infrastructure Metrics
1. 1
Why you should use
Elastic for Infrastructure
Metrics
Karl Degenhardt
Senior Solutions Architect
2. 2
Evolving Architectures ~↑ Monitoring Complexity
Hardware & software trends
are evolving in tandem
Higher resource utilization
increases monitoring complexity
• Orchestration/Hypervisor
• Dynamic/ephemeral jobs
• You can no longer "point" to
where that job lives
Shift to cloud-native yields
maintainable code, with costs
• Traditional licensing models don't scale
as well as your applications
• Hurdles with autoscaling
Monitoring Complexity
4. 4
• Support the full stack
• Easily ingest from new sources
• Monitor dynamic ecosystems
• Ability to interact with your data
– Aggregations and visualizations
– Different views based on who is looking
• Rich and flexible alerting
• Long term, reliable storage
• Bonus points for full Observability
Needs from a monitoring solution
Core features and functionally
7. 7
Instructions
right in Kibana
Growing list of integrations
● Download and install
Metricbeat
● Edit the configuration for
destination
● Enable and configure the
module
● Start the beats
● Explore!
8. 8
● Deploy Elastic Agent
● Choose the integration type
● Register and configure the data
source
● Specify the data you want to
collect
● Explore!
Elastic Fleet
Centralized ingest and configuration
9. 9
Use your existing shippers
Core features and functionality
Your App
Prometheus
Exporter
Your App
Prometheus
Exporter
Metricbeat +
Elasticsearch
Prometheus
Server
Metricbeat +
Elasticsearch Azure Monitor
10. 10
Autodiscover
Automatically monitor new containers
● Perfect for dynamic ecosystems
● Automatically picks up new
instances
● Works with K8s, Docker, AWS, etc.
● Hints based auto-discovery for K8s
● Full context backed by Elastic
Common Schema
15. ● Several types for numbers
double, integer, float
depending on size needs…
● Distributed Histograms (7.6
● IPs
query by IP/subnet
● Geo
Map your metrics
● Dates
Rich typing and
filtering
Much more than single type
numbers and string labels
16. Powerful aggregations
• Common metric aggs (sum, avg, count, min, max…)
• With more choices on top!
– Mutate data / calculate metrics at query time with scripting
– Grouping is not limited to labels: Geo proximity, filters, ranges
19. Distributed by design
• Horizontally scalable
• Cross cluster search
• Cross cluster replication
Easy to scale
20. 20
Powerful data store
Beyond Time Series
● Inverted index + columnar store
● Optimized numeric field types (BKD
● Powerful aggregations framework
● Fast response even for
high-cardinality queries
● ILM & Data Rollups
● With all of the benefits of the
Elastic Stack
24. 24
Integrated Alerting
Automatically detect and alert
● Many types of alerts
● Prefiltering based on context
● Multiple facets per alert
○ CPU and Memory
○ Network TX and RX
● Automatically split alerts on
chosen field (per
container/pod/host)
● Deviations in logging rates
25. 25
Machine Learning
Automatically detect and alert
● Automate anomaly detection at
scale and across disparate data
sources
● Find patterns in your logs
● Automatically call out anomalies
and outliers