---
title: "Ember Options"
description: "Additional configuration options for the Ember addon."
url: https://docs.sentry.io/platforms/javascript/guides/ember/configuration/ember-options/
---

# Ember Options | Sentry for Ember

All Sentry SDK options can be passed to `init`:

```javascript
import * as Sentry from "@sentry/ember";

Sentry.init({
  // Sentry options
  dsn: "___PUBLIC_DSN___",
});
```

The `@sentry/ember` add-on includes options to manage Ember specific instrumentation; these options are set on the add-on config directly.

```javascript
ENV["@sentry/ember"] = {
  // Ember specific options
};
```

The following documentation is for Ember specific configuration, for Sentry options, [see basic options](https://docs.sentry.io/platforms/javascript/guides/ember/configuration/options.md)

### [Tracing Considerations](https://docs.sentry.io/platforms/javascript/guides/ember/configuration/ember-options.md#tracing-considerations)

The Sentry tracing integration is already set up via the Ember add on with custom Ember instrumentation for routing, components, and the runloop. It sideloads Sentry tracing as a chunk to instrument your application. If you'd like to disable this automatic instrumentation and stop receiving the associated transactions, set `disablePerformance` in your config. See example below:

```javascript
ENV["@sentry/ember"] = {
  disablePerformance: true,
};
```

### [Routes](https://docs.sentry.io/platforms/javascript/guides/ember/configuration/ember-options.md#routes)

If you would like to capture timings for the `beforeModel`, `model`, `afterModel` hooks as well as `setupController` in one of your Routes, `@sentry/ember` exports a `instrumentRoutePerformance` function which can be used by replacing the default export with a wrapped Route.

```javascript
import Route from "@ember/routing/route";
import { instrumentRoutePerformance } from "@sentry/ember";

class MyRoute extends Route {
  model() {
    //...
  }
}

export default instrumentRoutePerformance(MyRoute);
```

### [Classic Components](https://docs.sentry.io/platforms/javascript/guides/ember/configuration/ember-options.md#classic-components)

The render times of classic components are also enabled by default, with a setting to capture render timings only above a certain duration. To change this minimum, you can modify `minimumComponentRenderDuration` in your config.

```javascript
ENV["@sentry/ember"] = {
  minimumComponentRenderDuration: 0, // Setting this to zero will capture all classic components.
};
```

To disable component instrumentation you can set `disableInstrumentComponents` in your config.

```javascript
ENV["@sentry/ember"] = {
  disableInstrumentComponents: true,
};
```

### [Runloop](https://docs.sentry.io/platforms/javascript/guides/ember/configuration/ember-options.md#runloop)

The duration of each queue in your application's runloop is instrumented by default, as long as the duration of the queue is longer than a threshold defined in your config by `minimumRunloopQueueDuration`

```javascript
ENV["@sentry/ember"] = {
  minimumRunloopQueueDuration: 0, // Setting this to zero will capture all runloop queue durations
};
```

If you would like to disable runloop instrumentation you can set `disableRunloopPerformance` in your config.

```javascript
ENV["@sentry/ember"] = {
  disableRunloopPerformance: true,
};
```