Two new sessions for OpenSearchCon Europe

_community_members/gkamat.md

@@ -0,0 +1,78 @@
+---
+#
+# Sample data for community members.
+#
+
+# The short name is used to identify related pieces of content in the site. For example it is used in the "authors" array of blog posts, and it is used in the "presenters" array for OpenSearch Conference sessions to identify who is speaking.
+# The format for existing values is not normalized. In some cases it is "first-initial-of-first-name" + "last-name", or matching a GitHub username, or something all together random. What is important is that it is unique within the system.
+short_name: "gkamat"
+
+# The member's full name, or otherwise meaningful preferred name. It is used in the templates for presenting content authors as well as the name of conference speakers.
+name: "Govind Kamat"
+
+# The path to the community member's photo.
+photo: '/assets/media/community/members/no-image-available.svg'
+
+# Used as the level 1 page header text.
+primary_title: 'Govind Kamat'
+
+# Used as the document title displayed in the browser title bar.
+title: 'OpenSearch Project Community Member: Govind Kamat'
+
+# Breadcrumbs specification.
+# The community icon is expected.
+# The breadcrumbs path structure is Communit -> Members -> First Last's Profile.
+breadcrumbs:
+  icon: community
+  items:
+    - title: Community
+      url: /community/index.html
+    - title: Members
+      url: /community/members/index.html
+    - title: "Govind Kamat's Profile"
+      url: '/community/members/govind-kamat.html'
+
+# Community member job title and company where they work.
+job_title_and_company: 'Database Engineer III - AWS OpenSearch'
+
+# Array of conference IDs for which the community member is a keynote speaker, if any, or boolean false otherwise.
+# This value is only relevant for member's with the "conference_speaker" user persona.
+#keynote_speaker:
+#  - '2023-north-america'
+# keynote_speaker: false
+
+# The conference topic track for the conference sessions that the user is a speaker. These are shaped as an array of value pairs mapping conference ID and name. 
+# For example for the North American conference for the year 2023, and the "Community" track:
+session_track: 
+  - conference_id: "2024-europe"
+    name: "Operating OpenSearch"
+
+# URL for the community member profile.
+permalink: '/community/members/govind-kamat.html'
+
+# Array of community member user personas.
+# At this time, only conference_speaker, and author are defined.
+personas:
+  - conference_speaker
+
+# Array of conference IDs that the member is a speaker.
+conference_id:
+  - "2024-europe"
+
+
+# Optional GitHub username
+#github: githubusername
+
+# Optional LinkedIn username
+#linkedin: linkedinusername
+
+# Optional Twitter username
+#twitter: twitterusername
+
+# Optional Mastodon server url, and username / handle.
+#mastodon:
+#  url: https://mastodon.social/@mastodonusername
+#  name: mastodonusername
+---
+
+Database Engineer III - AWS OpenSearch

_community_members/sdeshmukh.md

@@ -0,0 +1,78 @@
+---
+#
+# Sample data for community members.
+#
+
+# The short name is used to identify related pieces of content in the site. For example it is used in the "authors" array of blog posts, and it is used in the "presenters" array for OpenSearch Conference sessions to identify who is speaking.
+# The format for existing values is not normalized. In some cases it is "first-initial-of-first-name" + "last-name", or matching a GitHub username, or something all together random. What is important is that it is unique within the system.
+short_name: "sdeshmukh"
+
+# The member's full name, or otherwise meaningful preferred name. It is used in the templates for presenting content authors as well as the name of conference speakers.
+name: "Siddhant Deshmukh"
+
+# The path to the community member's photo.
+photo: "/assets/media/community/members/sdeshmukh.jpeg"
+
+# Used as the level 1 page header text.
+primary_title: 'Siddhant Deshmukh'
+
+# Used as the document title displayed in the browser title bar.
+title: 'OpenSearch Project Community Member: Siddhant Deshmukh'
+
+# Breadcrumbs specification.
+# The community icon is expected.
+# The breadcrumbs path structure is Communit -> Members -> First Last's Profile.
+breadcrumbs:
+  icon: community
+  items:
+    - title: Community
+      url: /community/index.html
+    - title: Members
+      url: /community/members/index.html
+    - title: "Siddhant Deshmukh's Profile"
+      url: '/community/members/siddhant-deshmukh.html'
+
+# Community member job title and company where they work.
+job_title_and_company: 'Senior Software Engineer, AWS'
+
+# Array of conference IDs for which the community member is a keynote speaker, if any, or boolean false otherwise.
+# This value is only relevant for member's with the "conference_speaker" user persona.
+#keynote_speaker:
+#  - '2023-north-america'
+# keynote_speaker: false
+
+# The conference topic track for the conference sessions that the user is a speaker. These are shaped as an array of value pairs mapping conference ID and name. 
+# For example for the North American conference for the year 2023, and the "Community" track:
+session_track: 
+  - conference_id: "2024-europe"
+    name: "Search"
+
+# URL for the community member profile.
+permalink: '/community/members/siddhant-deshmukh.html'
+
+# Array of community member user personas.
+# At this time, only conference_speaker, and author are defined.
+personas:
+  - conference_speaker
+
+# Array of conference IDs that the member is a speaker.
+conference_id:
+  - "2024-europe"
+
+
+# Optional GitHub username
+#github: githubusername
+
+# Optional LinkedIn username
+linkedin: scd
+
+# Optional Twitter username
+#twitter: twitterusername
+
+# Optional Mastodon server url, and username / handle.
+#mastodon:
+#  url: https://mastodon.social/@mastodonusername
+#  name: mastodonusername
+---
+
+I am a Senior Software Engineer in the AWS OpenSearch Core Search team. I am passionate about creating products and platforms from scratch and scaling them to handle extremely high volumes of data. In my free time I enjoy reading, playing pickleball and exploring new destinations.

_opensearchcon_sessions/2024-europe-a-thrilling-journey-into-data-driven-security-automation.md

@@ -1,7 +1,7 @@
 ---
 #
 # The expected filename format is ${conference_id}-${url-encoded-session-title}.md
-# For example the "Community Inclusion" session from the 2023 conference in North America the title is "2023-europe-community-inclusion.html"
+# For example the "Community Inclusion" session from the 2023 conference in Europe the title is "2023-europe-community-inclusion.html"
 #
 
 # Conference session speaker short name that maps to a short_name value
@@ -27,7 +27,7 @@ breadcrumbs:
       url: /events/opensearchcon/index.html
     - title: 2024
       url: /events/opensearchcon/2024/index.html
-    - title: North America
+    - title: Europe
       url: /events/opensearchcon/2024/europe/index.html
     - title: Session Summaries
       url: /events/opensearchcon/2024/europe/sessions/index.html

_opensearchcon_sessions/2024-europe-enhance-query-execution-visibility-in-OS-with-opentelemtry.md

@@ -0,0 +1,68 @@
+---
+#
+# The expected filename format is ${conference_id}-${url-encoded-session-title}.md
+# For example the "Community Inclusion" session from the 2023 conference in North America the title is "2023-north-america-community-inclusion.html"
+#
+
+# Conference session speaker short name that maps to a short_name value
+# in the community members collection.
+primary_presenter: 'sdeshmukh'
+
+# Conference session speaker full name.
+speaker_name_full: 'Siddhant Deshmukh'
+
+# Conference session title.
+speaker_talk_title: 'Enhance Query Execution Visibility in OS with OpenTelemetry'
+
+# Page level 1 header title.
+primary_title: 'Enhance Query Execution Visibility in OS with OpenTelemetry'
+
+# Page document title displayed in the browser title bar.
+title: 'OpenSearchCon 2024 Session: Enhance Query Execution Visibility in OS with OpenTelemetry'
+
+breadcrumbs:
+  icon: community
+  items:
+    - title: OpenSearchCon
+      url: /events/opensearchcon/index.html
+    - title: 2024
+      url: /events/opensearchcon/2024/index.html
+    - title: Europe
+      url: /events/opensearchcon/2024/north-america/index.html
+    - title: Session Summaries
+      url: /events/opensearchcon/2024/europe/sessions/index.html
+# Session date / time
+# The template logic expects the following format: YYYY-MM-DD - h:m(am|pm)-(h:m(am|pm))
+# The template logic expects the following format: YYYY-MM-DD - h:m(am|pm)-(h:m(am|pm))
+session_time: "time TBD"
+
+# Room of location where the talk will occur.
+session_room: "a room yet to be determined."
+
+# Session topic track.
+session_track: "Search"
+
+# URL permalink for the session.
+permalink: '/events/opensearchcon/sessions/enhance-query-execution-visibility-in-OS-with-opentelemetry.html'
+
+# ID of the YouTube video of the session to embed in the page.
+# This is to be added after the conference and after the session recordings
+# are uploaded to YouTube.
+#youtube_video_id: 'SOME_YOUTUBE_VIDEO_ID'
+
+# Conference ID.
+# It is normative to use the format of 'YYYY-location-name', eg. '2023-north-america'.
+conference_id: '2024-europe'
+
+# Array of short_name values for the Community Members with the conference_speaker persona whom are presenting the session. This includes the primary_speaker indicated above and any other presenters (if any).
+presenters:
+  - sdeshmukh
+
+---
+OpenSearch users and business today seek for visibility and insights into execution of their queries. Due to the multi-phase and distributed nature of these queries, pinpointing resource utilization and time consumption, as well as identifying bottlenecks, becomes exceedingly complex.
+
+Observability is the cornerstone of modern system monitoring and troubleshooting. In this session, we elucidate the pivotal role of observability in enhancing system reliability and performance. Delve into the three pillars of observability – Metrics, Logs, and Traces – gaining invaluable insights through real-world examples and use cases.
+
+Embark on a journey through OpenTelemetry, the cutting-edge observability framework revolutionizing the landscape of monitoring and diagnostics. Understand the necessity of OpenTelemetry in modern distributed systems, unraveling its key concepts such as context propagation, signals, and instrumentations. Explore the robust architecture of OpenTelemetry and its seamless integration with OpenSearch components, paving the way for comprehensive end-to-end observability solutions.
+
+Witness firsthand the practical application of OpenTelemetry within OpenSearch. Through insightful examples and code walkthroughs, learn how OpenTelemetry facilitates the effortless export of metrics and traces, offering unparalleled visibility into your OpenSearch clusters. Gain proficiency in leveraging OpenTelemetry to capture span and trace data, empowering you with actionable insights for optimizing system performance and reliability.

_opensearchcon_sessions/2024-europe-enhancing-ai-and-llm-systems-with-hybrid-search.md

@@ -17,7 +17,7 @@ breadcrumbs:
       url: /events/opensearchcon/index.html
     - title: 2024
       url: /events/opensearchcon/2024/index.html
-    - title: North America
+    - title: Europe
       url: /events/opensearchcon/2024/europe/index.html
     - title: Session Summaries
       url: /events/opensearchcon/2024/europe/sessions/index.html

_opensearchcon_sessions/2024-europe-multi-tenancy-for-all-workloads.md

@@ -27,7 +27,7 @@ breadcrumbs:
       url: /events/opensearchcon/index.html
     - title: 2024
       url: /events/opensearchcon/2024/index.html
-    - title: North America
+    - title: Europe
       url: /events/opensearchcon/2024/europe/index.html
     - title: Session Summaries
       url: /events/opensearchcon/2024/europe/sessions/index.html

_opensearchcon_sessions/2024-europe-unleash-your-clusters-potential-with-opensearch-benchmark.md

@@ -0,0 +1,72 @@
+---
+#
+# The expected filename format is ${conference_id}-${url-encoded-session-title}.md
+# For example the "Community Inclusion" session from the 2023 conference in North America the title is "2023-north-america-community-inclusion.html"
+#
+
+# Conference session speaker short name that maps to a short_name value
+# in the community members collection.
+primary_presenter: 'gkamat'
+
+# Conference session speaker full name.
+speaker_name_full: 'Govind Kamat'
+
+# Conference session title.
+speaker_talk_title: "Unleash Your Cluster's Potential with OpenSearch Benchmark"
+
+
+# Page level 1 header title.
+primary_title: Unleash Your Cluster's Potential with OpenSearch Benchmark
+
+# Page document title displayed in the browser title bar.
+title: "OpenSearchCon 2024 Session: Unleash Your Cluster's Potential with OpenSearch Benchmark"
+
+breadcrumbs:
+  icon: community
+  items:
+    - title: OpenSearchCon
+      url: /events/opensearchcon/index.html
+    - title: 2024
+      url: /events/opensearchcon/2024/index.html
+    - title: North America
+      url: /events/opensearchcon/2024/europe/index.html
+    - title: Session Summaries
+      url: /events/opensearchcon/2024/europe/sessions/index.html
+
+
+
+# The template logic expects the following format: YYYY-MM-DD - h:m(am|pm)-(h:m(am|pm))
+session_time: "time TBD"
+
+# Room of location where the talk will occur.
+session_room: "a room yet to be determined."
+
+
+# Session topic track.
+session_track: "Operating OpenSearch"
+
+# URL permalink for the session.
+permalink: '/events/opensearchcon/sessions/unleash-your-clusters-potential-with-opensearch-benchmark.html'
+
+# ID of the YouTube video of the session to embed in the page.
+# This is to be added after the conference and after the session recordings
+# are uploaded to YouTube.
+#youtube_video_id: 'SOME_YOUTUBE_VIDEO_ID'
+
+# Conference ID.
+# It is normative to use the format of 'YYYY-location-name', eg. '2023-north-america'.
+conference_id: '2024-europe'
+
+# Array of short_name values for the Community Members with the conference_speaker persona whom are presenting the session. This includes the primary_speaker indicated above and any other presenters (if any).
+presenters:
+  - gkamat
+
+---
+Are you confused about sizing your OpenSearch cluster? Worried whether it will scale to handle your workload? Curious if it's performing at its best? Unsure whether an upgrade will help? If so, this talk is tailored for you!
+
+OpenSearch users strive to obtain the best possible performance from their clusters to meet their business needs. However, measuring performance accurately and using the insights obtained to size, tune, and operate deployments is a complex undertaking.OpenSearch Benchmark (OSB), its associated workloads and provided telemetry devices are widely used within the community as a metric of performance. In this session, we'll dive into using OSB to model and run your workload, while comparing various scenarios, thereby providing you with the answers you need to optimize your cluster's performance. 
+
+You'll gain a deep understanding of OSB's capabilities, techniques for using it for performance, scale, and longevity tests, and how it's being leveraged for the community's performance runs. By mastering the effective use of this tool and customizing it to fit your unique needs, you'll obtain meaningful insights to unleash your OpenSearch cluster's full potential and meet your business goals.
+
+Join us and learn how to harness the power of OpenSearch Benchmark to maximize your cluster's performance, ensuring it scales seamlessly and operates at its peak.
+