BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Cloud Native Now - ECPv5.16.4//NONSGML v1.0//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-WR-CALNAME:Cloud Native Now
X-ORIGINAL-URL:https://cloudnativenow.com
X-WR-CALDESC:Events for Cloud Native Now
BEGIN:VTIMEZONE
TZID:America/New_York
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:20220313T070000
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
DTSTART:20221106T060000
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/New_York:20220330T150000
DTEND;TZID=America/New_York:20220330T160000
DTSTAMP:20260711T061620
CREATED:20220305T062744Z
LAST-MODIFIED:20220330T225432Z
UID:17093-1648652400-1648656000@cloudnativenow.com
SUMMARY:How to Simplify Kubernetes Monitoring on AWS
DESCRIPTION:Often\, logs\, metrics and traces that are clearly indicative of an upcoming production crisis are lost in the sea of telemetry data generated by modern\, distributed AWS environments. This is especially true in environments powered by technologies like Kubernetes. Each component in a microservices architecture\, such as databases\, cloud infrastructures\, backend and frontend services\, produces different kinds of telemetry data that must be monitored for performance and reliability.
URL:https://cloudnativenow.com/webinar/how-to-simplify-kubernetes-monitoring-on-aws/
ATTACH;FMTTYPE=image/png:https://cloudnativenow.com/wp-content/uploads/2022/03/2022-03-30-Logz.io-CJ-OnDemaondLandingPage@2x.png
END:VEVENT
END:VCALENDAR