---
title: ruby-agent-10-8-0
source: https://docs.newrelic.com/docs/release-notes/agent-release-notes/ruby-release-notes/ruby-agent-10-8-0
---

> #### ⚠️ IMPORTANT
>
> We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about [keeping agents up to date](https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/).
>
> See the New Relic Ruby agent [EOL policy](https://docs.newrelic.com/docs/apm/agents/ruby-agent/getting-started/ruby-agent-eol-policy/) for information about agent releases and support dates.

## v10.8.0

-   **Feature: Report a unique hostname for Google Cloud Run Worker Pools and Jobs**

    Cloud Run hostname support, added in [PR#3609](https://github.com/newrelic/newrelic-ruby-agent/pull/3609/), detected Cloud Run only through `K_REVISION`, the environment variable set by Cloud Run **Services**. The agent now also recognizes [`CLOUD_RUN_REVISION`](https://docs.cloud.google.com/run/docs/container-contract#env-vars) (Worker Pools) and `CLOUD_RUN_EXECUTION` (Jobs), so `utilization.gcp_cloud_run.use_instance_as_host` now applies to all three resource types. When `utilization.gcp_cloud_run.include_revision_in_host` is `true`, the hostname is built from whichever of these variables is present — for example, `{CLOUD_RUN_EXECUTION}-{instance id}` for a Job. [Issue#3651](https://github.com/newrelic/newrelic-ruby-agent/issues/3651) [PR#3652](https://github.com/newrelic/newrelic-ruby-agent/pull/3652)

-   **Feature: Add `browser_monitoring.version` configuration option**

    Customers can now pin the exact browser agent loader version New Relic injects by setting the new `browser_monitoring.version` configuration option. See the [browser agent EOL policy](https://docs.newrelic.com/docs/browser/browser-monitoring/getting-started/browser-agent-eol-policy/) for which versions are currently available and supported. [PR#3663](https://github.com/newrelic/newrelic-ruby-agent/pull/3663)

-   **Feature: Add span.kind to background job libraries**

    Now, the `span.kind` attribute will be added to `produce` and `consume` operations from background job libraries. This includes ActiveJob, Sidekiq, Resque and DelayedJob. [PR#3636](https://github.com/newrelic/newrelic-ruby-agent/pull/3636)

-   **Bugfix: DelayedJob instrumentation no longer reinstalls itself on every worker under prepend mode**

    When DelayedJob instrumentation is installed via prepend (the default), creating more than one `Delayed::Worker` in the same process caused the agent to log "Installing DelayedJob instrumentation" and reinitialize the plugin again for each additional worker. This was harmless but noisy; it's now only done once per process, matching the existing chain-instrumentation behavior. [PR#3654](https://github.com/newrelic/newrelic-ruby-agent/pull/3654)

-   **Bugfix: Allowlisted configuration values are no longer case sensitive**

    Previously, allowlisted configuration options required an exact case match, so a value with unexpected casing — like `OBFUSCATED` or `ObFuScAtEd` for `slow_sql.record_sql` — would silently fall back to the default. Configuration options that validate against an allowlist now match values regardless of case, so both are treated the same as `obfuscated`. [Issue#3613](https://github.com/newrelic/newrelic-ruby-agent/issues/3613) [PR#3645](https://github.com/newrelic/newrelic-ruby-agent/pull/3645)

-   **Bugfix: Puma instrumentation works when Puma is lazy-loaded**

    With `gem "puma", require: false`, Puma was not yet loaded when the agent's dependency check ran, so Puma instrumentation would fail to install. The agent now recognizes `Puma::RackHandler` as evidence that Puma is present, fixing this issue. [Issue#3641](https://github.com/newrelic/newrelic-ruby-agent/issues/3641) [PR#3650](https://github.com/newrelic/newrelic-ruby-agent/pull/3650)