Slide 1

Slide 1 text

V0000000 Ask an Openshift Admin February 15, 2023 Openshift Logging and Observability 1

Slide 2

Slide 2 text

V0000000 Disclaimer The content set forth herein is Red Hat confidential information and does not constitute in any way a binding or legal agreement or impose any legal obligation or duty on Red Hat. 2 This information is provided for discussion purposes only and is subject to change for any or no reason.

Slide 3

Slide 3 text

V0000000 Deliver ONE unified, consistent, and simplified Observability experience across any footprint: the public cloud, on-prem, and edge Our Observability Strategy 3

Slide 4

Slide 4 text

V0000000 4 Store: Metrics with Prometheus/Thanos Logs with Loki Traces with Jaeger/Elasticsearch Observability "Turn your data into answers!" Data Visualization Data Analytics Data Delivery Data Storage Visualize: Out of the box experience & full support in OpenShift Web Console Collect: Metrics with Prometheus Logs with Vector Traces with OpenTelemetry Product Manager: Jamie Parker, Roger Floren & Vanessa Martini Data Collection Deliver: Aggregate & Normalize data Transport it with Observability Operator Analyze: Query metrics Search metrics targets Filter logs by severity 1 2 3 5 4 OpenShift Observability Third Party Integration

Slide 5

Slide 5 text

V0000000 Observability Metrics Logs Traces Monitoring OpenShift 4.12 Logging v5.6 Q42022 Logging Distributed Tracing ● Support for forwarding logs to Splunk ● Support for forwarding logs to Google Cloud Platform ● Add the openshift cluster ID to log records so that clusters can be uniquely identified in aggregated logs ● GA release of Vector as an alternate collector to Fluentd ● Exposed stream-based retention capabilities in the Loki Stack custom resource for OpenShift Application owners and OpenShift Administrators ● Log Exploration UI also available in OpenShift Developer Console ● Improved UI experience in OpenShift Console: > Custom time range > Predefined filters to easily search and filter logs (namespace, pod, container) ● OpenTelemetry as Traces Collector (now in Tech Preview) ● Multi-cluster support in OpenTelemetry ● Kubernetes Attribute Processor ● Option to specify Topology Spread Constraints for Prometheus, Alertmanager, and Thanos Ruler. ● Option to improve consistency of prometheus-adapter CPU and RAM time series. ● TP: Allow admin users to create new alerting rules based on platform metrics ● Version updates to monitoring stack components and dependencies ● Runbooks URLs enabled in the Alerting UI of OpenShift Console ● Improved UI experience in OpenShift Console: > Easier selection of records in Metrics UI 5

Slide 6

Slide 6 text

V0000000 Upstream Projects Contribution 6 Grafana Loki for log aggregation https://grafana.com/oss/loki/ Vector for log collection https://vector.dev/ Prometheus for metrics https://prometheus.io/ Thanos for metrics https://thanos.io/ Jaeger for distributed tracing https://www.jaegertracing.io/ OpenTelemetry for standardizing data https://opentelemetry.io/ Grafana Tempo for traces https://grafana.com/oss/tempo/ Kafka for event streaming https://kafka.apache.org/intro

Slide 7

Slide 7 text

V0000000 OpenShift Logging 7

Slide 8

Slide 8 text

V0000000 Initial Openshift Logging Stack 8 Elasticsearch ● Log Store ● Log Search Fluentd ● Log Collection ● Log Transportation Kibana ● Log Visualization

Slide 9

Slide 9 text

V0000000 Current Openshift Logging Stack 9 Vector as collector Loki as log store ▸ Loki indexes log labels instead of log lines for better performance ▸ Log visualization natively inside the OpenShift Console ▸ Vector has excellent Log Per Second performance Major updates and features ▸ Pod labels for k8s are preserved ▸ Support Cloudwatch output for Vector ▸ CloudWatch log forwarding add-on supports STS installations ▸ Loki allows multiple tenants to use a single Loki instance.

Slide 10

Slide 10 text

V0000000 Openshift Logging - Vector Collection 10 AWS Cloudwatch GCP Stackdriver Loki Splunk

Slide 11

Slide 11 text

V0000000 Openshift Logging - Loki Storage 11 ● LogQL query language ● Efficient memory use via log chunking ● Multi tenant storage with data isolation ● Cluster ID added for easier log aggregation ● When used as the Openshift log store, enables log analytics within the Openshift console UI

Slide 12

Slide 12 text

V0000000 New entry: Aggregated Logs view in Developer Console PMs: Roger Floren, Jamie Parker & Vanessa Martini Improved UX: Filter by content (namespace, pod, container) AND Search by content AND Filter by severity OpenShift Observability 12

Slide 13

Slide 13 text

V0000000 The Future 13

Slide 14

Slide 14 text

V0000000 14 Upcoming on the Roadmap Vector ● Http Forwarding ● Syslog Forwarding ● Multicluster Collection Loki ● Log based alerting ● Zone aware replication Console UI ● Even more log viewing and aggregation enhancements ● Correlation

Slide 15

Slide 15 text

V0000000 15 OpenShift 4.12 / Logging 5.6 Blog Logging 5.5 Blog Notable Blogs OpenShift Monitoring for 4.12 Blog Network Observability Support in OpenShift 4.12 Blog Red Hat OpenShift Observability Brings Flexible Insights to Management of Clusters Blog In-depth OpenShift Monitoring for 4.12 Blog What is OpenTelemetry? Blog

Slide 16

Slide 16 text

V0000000 linkedin.com/company/red-hat youtube.com/user/RedHatVideos facebook.com/redhatinc twitter.com/RedHat 16 Red Hat is the world’s leading provider of enterprise open source software solutions. Award-winning support, training, and consulting services make Red Hat a trusted adviser to the Fortune 500. Thank you