BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//OpenSearch - ECPv6.16.2//NONSGML v1.0//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-WR-CALNAME:OpenSearch
X-ORIGINAL-URL:https://opensearch.org
X-WR-CALDESC:Events for OpenSearch
REFRESH-INTERVAL;VALUE=DURATION:PT1H
X-Robots-Tag:noindex
X-PUBLISHED-TTL:PT1H
BEGIN:VTIMEZONE
TZID:UTC
BEGIN:STANDARD
TZOFFSETFROM:+0000
TZOFFSETTO:+0000
TZNAME:UTC
DTSTART:20220101T000000
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=UTC:20230426T133000
DTEND;TZID=UTC:20230426T143000
DTSTAMP:20260526T173239
CREATED:20250107T193130Z
LAST-MODIFIED:20250107T193140Z
UID:10000184-1682515800-1682519400@opensearch.org
SUMMARY:Upgrading Log-Analytics Clusters to OpenSearch
DESCRIPTION:Join Amitai Stern at the Real-Time Analytics Summit for the session “Upgrading Log-Analytics Clusters to OpenSearch”\nHere at Logz.io\, the open-source observability and security company\, we manage observability data for over 1300 companies in highly scalable multi-cloud deployments. With the Elasticsearch license changes of 2021 we needed to migrate to an open-source platform\, and OpenSearch was where we were going to contribute and what we wanted to run in production. \nMany equate upgrading to OpenSearch from Elasticsearch in production as changing the tires on a moving bus. Upgrading has many risks\, and if the cluster is in continuous production use\, ingesting terabytes of data daily\, the risks can seem overbearing. \nIn this talk\, we will cover multiple upgrade strategies\, including version requirements\, and their pros and cons. Additionally\, we will cover a different option\, which is the way we\, at Logz.io\, upgraded all our clusters to OpenSearch without significant extra costs while minimizing risk. Not only did we upgrade to OpenSearch\, but we also migrated our AWS workloads to Graviton2 instances. \n 
URL:https://opensearch.org/event/2023-0426-rta-sumit/
CATEGORIES:Events
ATTACH;FMTTYPE=image/png:https://opensearch.org/wp-content/uploads/2025/01/OpenSearch-Feature-Image.png
END:VEVENT
END:VCALENDAR