elixirconf

AppSignal at ElixirConf 2026

AppSignal at ElixirConf 2026

Today marks the start of ElixirConf 2026 in Chicago. We here at AppSignal couldn’t be more excited to see the sessions and see what’s new. Several of our team members are attending in person and virtually.

If you’re at the event and you see our CEO, Brandon, say hi! We’d love to chat and get to know you!

Brandon Swalve, CEO of AppSignal

As attendees think about how they’ll build the next evolution of their Elixir apps, I wanted to share a few things we’ve done to make it easy to ensure your applications are fully monitored and can launch to production with peace of mind.

Our Elixir integration

For those who are unaware of our Elixir capabilities, we have a wonderful native integration that unlocks access to monitoring:

The Erlang dashboard in AppSignal, showing IO, schedulers, processes, memory, atom usage, and scheduler utilization

Getting started, with or without an agent

Getting started is easier than ever; you can add your Elixir application in a few steps or hand these instructions to your agent to instrument it for you. Point your agent to installation guide for coding agents and use the agent-friendly instructions provided.

Handing the AppSignal install instructions to a coding agent: “Install AppSignal in this application. Download, read and follow https://docs.appsignal.com/agents/new-application.md, doing every step in order.”

These instructions work for LLMs of your choice, including those provided by Claude, Google, OpenAI, or even self-hosted Qwen models.

Bring your monitoring data to your AI

After instrumenting your application, you can use the AppSignal context store for your coding agents and while triaging your errors with your AI of choice.

That context store is the foundation the rest of AppSignal Intelligence is grounded in. It’s what lets us build a dashboard for you the moment we spot an integration like Ecto, what Time Detective reads to reconstruct your app at any moment in the past, and what the MCP endpoint and CLI hand to your agent. One set of grounded context, whichever way you reach for it.

You can connect the AppSignal context store to your preferred LLM via our MCP-hosted endpoint or our CLI.

With one line of configuration:

Shell
claude mcp add --transport http appsignal https://appsignal.com/api/mcp

Claude can now use the monitored context about the errors, metrics, traces, logs, and more from your Elixir application. Investigating incidents when your application goes offline in the middle of the night can start with a conversation.

Come say hi

We hope you enjoy ElixirConf, and we would be thrilled to see you there or connect virtually!

Interested in what’s next on our roadmap? Check out our AppSignal Labs page and join our Discord. We’d love to hear what’s important to you and whether we’re building towards something you need!

Looking for what we do for startups? Check whether you’re eligible for our startup program.

Published

Wondering what you can do next?

  • Share this article on social media
Serena Chou

Serena Chou

Obsessed with building intuitive customer-first products, communities and climbing rocks. Always excited to hear from developers on what they need to innovate, come chat any time.

All articles by Serena Chou

Become our next author!

Find out more
$appsignal install

AppSignal monitors your apps

AppSignal provides insights for Ruby, Rails, Elixir, Phoenix, Node.js, Express and many other frameworks and libraries. We are located in beautiful Amsterdam. We love stroopwafels. If you do too, let us know. We might send you some!

Discover AppSignal