Raygun APM Agent 3.0.14: faster, simpler, and ready for ARM64

By Phillip Haydon | Posted Aug 24, 2026 | 5 min. (952 words)

Today we are releasing Raygun APM Agent 3.0.14 for Windows, Linux, and Azure App Service.

This release is the result of a substantial modernization of the Agent, profiler, installers, and release pipeline. It makes Raygun APM easier to deploy, reduces overhead in several critical paths, adds native Linux ARM64 support, and lets developers investigate APM data through Raygun API v3 and the Raygun MCP server.

If you are upgrading from version 2.3.0, there is much more here than a version-number change.

A faster, more resilient APM pipeline

An APM agent has to collect useful detail without becoming part of the performance problem. For 3.0.14, we reviewed the full path from profiler callbacks through the Agent processing pipeline and into Raygun.

The result includes:

  • Less locking and contention in profiler hot paths
  • Batched, rate-limited communication between the profiler and Agent
  • Bounded queues and backpressure to protect applications during bursts
  • Lower allocation costs when processing and removing trace frames
  • More efficient Agent parsing, correlation, and post-processing
  • Better supervision of UDP and TCP receivers
  • Improved async, database, and provider trace correlation

In representative managed-pipeline benchmarks, the updated Agent sustained approximately 10% more throughput than the 2.3.0 baseline. Targeted profiler benchmarks also showed substantial reductions in callback overhead and contention.

We have kept ReadyToRun and NGen support enabled. This avoids forcing applications to fully JIT compile at startup and helps preserve normal application startup and CPU behavior.

Communication has been simplified

The profiler and Agent now use two supported transport modes: UDP and TCP. We removed the old named-pipe path and simplified the communication lifecycle around the transports that we actively support.

This work is not only cleanup. Receivers are supervised, callback failures are isolated, and profiler traffic is batched before it is sent. These changes make the connection more predictable while limiting the amount of work performed on application threads.

Azure App Service needs a slightly different approach. The profiled application and the Agent WebJob run in separate Azure sandboxes, so normal loopback or private-IP unicast traffic cannot reliably cross that boundary. The Raygun Azure extension now selects an available port during installation and uses Azure-specific UDP multicast to connect the two processes.

There is no fixed port to configure, and the behavior is limited to Azure App Service. Standard Windows and Linux installations continue to use local communication.

One version across every component

Agent 3.0.14, Profiler 3.0.14, Windows MSI 3.0.14, Linux 3.0.14, and the Azure App Service extension 3.0.14 now describe the same release.

That sounds simple, but it removes a common source of confusion when diagnosing an installation. The Windows, Linux, and Azure packages are built from a shared version and verified through the same release lineage before publication.

One-command installation

The production installers now resolve the latest supported release, download the correct package, verify it, install it, and check that the Agent starts successfully.

On Linux, run:

curl -fsSL https://downloads.raygun.com/apm/install.sh | sudo sh

The Linux installer detects the machine architecture, selects the matching package, verifies its SHA-256 digest, installs it atomically, and configures systemd, OpenRC, or SysV init as appropriate.

On Windows, open an elevated PowerShell session and run:

Invoke-RestMethod https://downloads.raygun.com/apm/install.ps1 | Invoke-Expression

The Windows installer verifies both the package checksum and Authenticode signature before running the MSI. It also supports upgrades and repair more cleanly, and uninstalling the Agent no longer forces IIS to stop or restart. This leaves application lifecycle decisions with the operator.

The installers do not store a global Raygun application API key. Each profiled application keeps its own API key and profiler configuration, so one Agent can safely receive data from multiple applications.

Native Linux ARM64 support

Raygun APM now includes native Linux ARM64 builds of both the Agent and profiler, alongside the existing AMD64 release.

There is no separate ARM installer. The same Linux command detects x86_64, amd64, aarch64, or arm64 and downloads the correct artifact. The release pipeline verifies both architectures across the supported Linux distribution matrix before the version is promoted.

This makes the same APM deployment workflow available on ARM-based cloud instances without requiring emulation or a custom installation process.

Investigate APM data through API v3 and MCP

Collecting better traces is only useful if developers can get to the answer quickly. Raygun API v3 now exposes APM investigation capabilities, and the same capabilities are available to AI coding tools through the Raygun MCP server.

The new APM tools can:

  • Search traces by time, request, duration, and status
  • Investigate an individual trace, including slow calls and linked issues
  • Find recurring performance issues and anti-patterns
  • Rank database queries, external calls, and methods by total time, average duration, or call count
  • Surface percentile data and links back to Raygun for deeper investigation

For example, after connecting Raygun MCP to your coding agent, you can ask:

Find the slowest requests in my application over the last 24 hours and show me which database queries contributed the most time.

Or:

Investigate recent failed requests for this endpoint, identify the recurring APM issue, and show me the affected traces.

The MCP tools return bounded, paged, and privacy-conscious results. Sensitive arguments, variables, query values, and path data are omitted or redacted, and access is controlled by your Raygun Personal Access Token and application permissions.

To connect Cursor, Codex, or another MCP-compatible client, use:

https://api.raygun.com/v3/mcp

See our Raygun MCP setup guide for configuration examples.

Available now

Raygun APM Agent 3.0.14 is available now through the production Windows and Linux installers. Version 3.0.14 of Raygun.AzureAppService.Extension is also available from the production NuGet feed for Azure App Service deployments.

This release gives the APM platform a cleaner foundation: one version, fewer moving parts, broader architecture support, a faster data path, and a much shorter route from a performance symptom to an answer.