Skip to content


Docs have been moved to the atlas-docs site. This page is no longer maintained.

Netflix Integration

When running at Netflix, use the atlas-client library to enable transferring the instrumented data to Atlas. See the appropriate section for the type of project you are working on:


For libraries, the only dependency that should be needed is:${version}

The bindings to integrate internally should be included with the application. In your code, just inject a registry, e.g.:

public class Foo {
  public Foo(Registry registry) {

See the testing docs for more information about creating a binding to use with tests.

Libraries should not install SpectatorModule. The bindings to use for the registry should be determined by the application that is using the library. Think of it as being like slf4j where logging configuration is up to the end-user, not the library owner.

When creating a Guice module for your library, you may want to avoid binding errors if the end-user has not provided a binding for the Spectator registry. This can be done by using optional injections inside of the module, for example:

// Sample library class
public class MyLib {
  Registry registry;

  public MyLib(Registry registry) {
    this.registry = registry;

// Guice module to configure the library and setup the bindings
public class MyLibModule extends AbstractModule {

  private static final Logger LOGGER = LoggerFactory.getLogger(MyLibModule.class);

  protected void configure() {

  private MyLib provideMyLib(OptionalInjections opts) {
    return new MyLib(opts.registry());

  private static class OptionalInjections {
    @Inject(optional = true)
    private Registry registry;

    Registry registry() {
      if (registry == null) {
        LOGGER.warn("no spectator registry has been bound, so using noop implementation");
        registry = new NoopRegistry();
      return registry;


Application should include a dependency on the atlas-client plugin:


Note this is an internal only library with configs specific to the Netflix environments. It is assumed you are using Nebula so that internal maven repositories are available for your build. When configuring with governator specify the AtlasModule:

Injector injector = LifecycleInjector.builder()
    .withModules(new AtlasModule())

The registry binding will then be available so it can be injected as shown in the libraries section. The insight libraries do not use any governator or guice specific features. So it is possible to use guice or other dependency injection frameworks directly with the following caveats:

  1. However, some of the libraries do use the @PostConstruct and @PreDestroy annotations for managing lifecycle. Governator adds lifecycle management and many other features on top of guice and is the recommended way. For more minimalist support of just the lifecycle annotations on top of guice see iep-guice.
  2. The bindings and configuration necessary to run correctly with the internal setup are only supported as guice modules. If trying to use some other dependency injection framework, then you will be responsible for either finding a way to leverage the guice module in that framework or recreating those bindings and maintaining them as things change. It is not a paved road path.

Base Server

If using base-server, then you will get the Spectator and Atlas bindings automatically.

Auto Plugin


Deprecated: Use of AutoBindSingleton is generally discouraged. It is recommended to use one of the other methods.

If you are only interested in getting the GC logging, there is a library with an auto-bind singleton that can be used:${version}

Assuming you are using karyon/base-server or governator with in the list of base packages then the plugin should get automatically loaded.