The Elastic Developer Relations Team will be in town for PyOhio, and we will be hosting a meetup after the conference on Monday, July 28th, 2025.
Our incredible Senior Developer Advocate Jessica Garson will be the MC of the night and we'll have presentations from Chase Horvath (Staff Solutions Engineer at Confluent) and Eddie Mitchell (Search Data Developer at Summit Racing), followed by networking, pizza, and refreshments.
📅Date and Time:
Monday, July 28th, from 5:30-7:30 PM
📍Location:
Artemis Staffing - 6161 Oak Tree Blvd, Ste 300 Independence, OH 44131
The meetup will take place in a conference room in Suite 300 (head to the 3rd floor upon arrival)
⚡️ Interested in giving a talk? ⚡️
Have you ever considered presenting on your Elastic use case? We welcome 5-10 minute lightning talks, 45-minute deep dives, and everything in between. If you're interested, please send us an email at meetups@elastic.co.
🚗 Parking:
- Please be sure to not park in the other building tenants' parking spots.
- Please park in any of Artemis' parking spots to the left of the building against the green space.
🪧 Arrival Instructions:
Once you get to the building, take the elevator to the third floor and the meeting room is on your right when you get off the elevator.
📝 Agenda:
- 5:30 pm: Doors open
- 6:00 pm: Talk # 1 - Visualizing video game telemetry without breaking the bank
Chase Horvath - Staff Solutions Engineer at Confluent
Abstract: Games generate massive data streams, and many game studios rely on Kafka to ingest it. Cost is a limiting factor on the granularity of data they can collect, but more data leads to better decision making and a better player experience. Replacing traditional kafka with Confluent Freight clusters will reduce the cost of telemetry ingestion and still allow Studios to use downstream tools, like Elastic Cloud, to work with the data in near real time. Attendees will learn about the integration of Elastic Cloud and Confluent Freight, as well as gain some insights into what makes their favorite games come to life.
- 6:30 pm: Talk #2 Who am I to judge? AI Judgements and Learn to Rank in Elasticsearch
Eddie Mitchell - Search Data Developer at Summit Racing
Abstract: Welcome to the next stop in my journey of Search and Relevance - Judgements and Learn To Rank! What are judgements? Why am I being judged? Or wait, am I the one being judge-y? Well, who am I to judge?? And what does this have to do with Learn to Rank?
If you're having these questions - at least about Search - then join me as we talk through some of these topics and try to make them make sense.
What I found out pretty quickly: judgements are important! Not only are they the basis of the Learn To Rank features, but they're also foundational to how we determine if our search is actually working. The problem? They can be really hard to get. You need someone to look at many query/document pairs and say "yes, this is relevant" or "nope, this doesn't help the user." But for the vast majority of queries that I encounter, I'm not a subject matter expert. So, who am I to judge what's relevant?
That's where I started experimenting with AI as a judge. I'll show you some manual prompt engineering I tried, and then dive into a tool called Quepid (from OpenSourceConnections) that I use which has integrated "AI as a judge" into the query development workflow and has been pretty awesome for me.
Before we wrap up, we'll talk about the Learn To Rank in Elasticsearch and see if we can't get some judgements to power a quick LTR demo.
This isn't a polished solution - it's me figuring out the judgment problem as I go, sharing what's working, what isn't, and hoping to get some ideas from all of you about where to take this next.
- 7:00 pm: Lightning Talk #3 How to create a customized running plan using Python, Elasticsearch, and Agno
Jessica Garson - Senior Developer Advocate at Elastic
Abstract: When working out, deciding what workout to do next to achieve a specific goal can be challenging. This talk post will guide you through creating a four-week workout plan as a Notion page with to-do list items tailored to your workout history, helping you run a faster 5K.
- 7:10-7:30 pm: Networking
