Grafana & Friends Singapore x Docker - Nov 2026

👋 Hello Grafana & Friends Singapore!
This month, we are excited to partner with Docker and Grafana Labs for a collaborative evening of tech! Special shoutout to our community partners, Workato for this event.
As coding agents take on more of the day-to-day engineering work, the questions of where they run, what they can access, and how you observe what they're doing are becoming just as important as the code they write.
This month, we are bringing together engineers from the Docker and Grafana ecosystems to share practical implementation strategies and real-world patterns.
As always, come ready to learn, connect, and exchange ideas with the community.

🎤 Topic 1: YOLO mode needs plumbing: building agent integrations with Docker Sandboxes

Speaker: Oleg Selajev, Developer Advocate, Docker
Session Abstract:
Letting a coding agent install tools, run commands, and keep working without asking permission is a tempting way to get things done. But it still needs somewhere to run, access to the right services, and a setup you can reproduce without handing over your entire laptop.
We'll start with Docker Sandboxes: how they give agents room to work, what the isolation boundary protects, and how agents connect to the tools and services they need. Then we'll introduce Sandbox Kits to package those environments so each developer doesn't have to assemble and maintain their own collection of setup scripts.
We'll walk through building a Grafana integration that instruments the coding agent itself and sends its traces to Grafana. That means installing the tools, configuring how the agent starts, and handling credentials and network access inside the sandbox.
We'll also cover what belongs in a reusable kit, what stays specific to a developer or project, and what happens when dependencies change. You'll leave knowing how to build your own integrations and what you'll need to maintain once other people start using them.

🎤 Topic 2: Why Keep Docker Build Traces When Docker Already Shows Them?

Speaker: Yoshi Yamaguchi, Staff Developer Advocate, Grafana Labs
Session Abstract: Docker builds get slower one commit at a time, and you rarely know which commit caused it. BuildKit already records an OpenTelemetry trace of every build, and docker buildx history trace opens that trace in Jaeger. That view shows one build on one machine. By default, the builder keeps the latest 50 build records and removes older ones only after 48 hours. An ephemeral CI runner loses that history when the job ends.
In this session, I send the same traces to Grafana Tempo with two environment variables on the builder, and I keep every build. With that history, a TraceQL metrics query shows when the build time jumped. A commit ID on each trace then points to the change, and the trace shows which step got slower. A coding agent can do the same work through the Grafana MCP server. It searches the traces, finds the commit, fixes the Dockerfile, and checks the new build. For a single build on your laptop, Docker's own view is quicker.
After this session, you can send your build traces to Tempo and decide when the local view is enough.

📌 Event Details

📅 Date: Tuesday, November 3rd, 2026
🕡 Time: 6:30pm - 9:00pm
📍 Location: Workato Singapore, Level 22, Suntec Tower 4
⚠️ Registration: Please register at the lobby first, then come up.

Have a physical NRIC or Passport? Use a kiosk to register.
Only have Singpass? Register with the receptionist.

🗓️ Agenda

6:30 PM: Registration, Light Bites & Networking
7:00 PM: Welcome & Opening
7:15 PM: Oleg Selajev, Developer Advocate at Docker – YOLO mode needs plumbing: building agent integrations with Docker Sandboxes
8:00 PM: Yoshi Yamaguchi, Staff Developer Advocate at Grafana Labs - Why Keep Docker Build Traces When Docker Already Shows Them?
9:00 PM: Networking & Close