The Architecture of Agentic AI

We're excited to bring the community together for an evening of learning and connection!
Come support your fellow developers, learn something new, and meet others who are passionate about search, observability, and security.

Date and Time:
Wednesday, August 19th, from 5:30-7:30 pm

Agenda:

• 5:30 pm: Doors open; say hi, grab a seat, and eat some food.
• 6:00 pm: Elasticsearch as a knowledge hub: Context engineering in practice, by Akanksha Singh,
  Senior Solutions Architect at Elastic
• 6:30 pm: Q&A
• 6:40 pm: What happens when AI meets your APIs? by John Tobin, Technical Product Leader at Virtual Guardian
• 7:10 pm: Q&A with John
• 7:20-7:30 pm: Networking & refreshments

Talk Abstracts:
Elasticsearch as a Knowledge Hub: Context Engineering in Practice
In this session, we’ll explore how context engineering helps solve this retrieval problem by making the right organizational knowledge available at the right time, for both people and AI agents. We’ll also show how Elastic brings together the key components needed to build this layer, without the complexity of stitching together multiple tools. We'll learn:

• Real-world use cases for context engineering across organizations
• How Elastic uses context engineering internally on our own documents and decisions
• A live demo of MCP grounding AI agents in your organization’s actual decisions and history
• Practical starting points for improving knowledge management with Elastic

What happens when AI meets your APIs?
APIs are ever more important in the age of Agentic AI. Monitoring APIs for performance and security is critical for any organization as APIs power our websites, mobile applications, partner integrations, cloud orchestrations, and more. This is especially vital now, however, because APIs are the 'action plane' of Agentic AI. In this session, we will demonstrate how we can use the tools in the latest Elastic release to help us with this task. You will learn the importance of API security and how instrumenting API entry points can be a solution to monitoring API and AI traffic. You will also see how some of the latest features can help, and how Elastic:

• Makes log ingestion easy, to surface API audit information to interested parties in the organization.
• AI Agents can help diagnose security and operational issues for even junior security analysts.
• Operational SLOs can help spot performance problems in the daily 'noise' of API traffic.
• Machine learning can help predict and identify unexpected use.
• Workflows can help users take action in the event of API operational or security issues, or if AI Agents start to misbehave!

Location:
Improving Office
171 East Liberty St
Unit 235
Toronto, Ontario M6K 3P6

Directions (171 E Liberty St - Suite 235)
By transit
Streetcars 504 and 509 both travel close to the office (less than 10 minute walk to the office from either), the lakeshore GO train is also a 5 minute walk from the office.
By car/parking
On street parking is available - there are a handful of paid parking spots directly in front of the entrance - with a large city parking lot across the street.

Entrance
The entrance to the office is beside the Bulk Barn entrance facing Hannah Street. There is an Improving logo on the door.