Client library for collecting metrics.
Java Other
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
codequality IpcLogger to help with using IPC metrics (#586) Jul 18, 2018
docs update docs to refer to 0.69.0 (#575) Jun 13, 2018
gradle/wrapper update to gradle 4.9 (#590) Jul 26, 2018
scripts update gh-pages helper script Apr 14, 2016
spectator-agent delay resolving agent configs (#553) May 19, 2018
spectator-api add stateless registry for FaaS use-cases (#595) Aug 10, 2018
spectator-ext-aws add Automatic-Module-Name to manifest (#515) Jan 27, 2018
spectator-ext-aws2 add Automatic-Module-Name to manifest (#515) Jan 27, 2018
spectator-ext-gc add Automatic-Module-Name to manifest (#515) Jan 27, 2018
spectator-ext-ipc initial version of servlet filter for ipc metrics (#598) Aug 10, 2018
spectator-ext-ipcservlet fix AbstractMethodError on older servlet-api (#599) Aug 10, 2018
spectator-ext-jvm give ObjectName props priority over attributes (#602) Aug 20, 2018
spectator-ext-log4j1 add Automatic-Module-Name to manifest (#515) Jan 27, 2018
spectator-ext-log4j2 add Automatic-Module-Name to manifest (#515) Jan 27, 2018
spectator-ext-placeholders allow counters to accept floating point delta (#547) May 8, 2018
spectator-ext-sandbox Helper method to specify the gzip compression level (#536) Apr 9, 2018
spectator-ext-spark add max gauge type to registry (#548) May 9, 2018
spectator-nflx-plugin always use AtlasRegistry (#593) Aug 9, 2018
spectator-nflx update nflx plugin to use archaius2 (#525) Feb 23, 2018
spectator-perf add Automatic-Module-Name to manifest (#515) Jan 27, 2018
spectator-reg-atlas limit use of step clock to gauges (#600) Aug 15, 2018
spectator-reg-metrics3 update totalTime for metrics3 Timer (#580) Jun 27, 2018
spectator-reg-servo fix illegal reflective access for ServoIdTest (#563) May 30, 2018
spectator-reg-stateless add stateless registry for FaaS use-cases (#595) Aug 10, 2018
spectator-web-spring do not force update of polled gauges inline (#562) May 30, 2018
.gitignore add wiki/site dir to .gitignore Apr 2, 2016
.netflixoss use jdk 1.8 Aug 6, 2015
.travis.yml update travis to build on openjdk10 (#592) Jul 26, 2018 Need a for bintray automation Jan 23, 2015 add contributing guide (#489) Oct 26, 2017
LICENSE add license file Dec 4, 2014
OSSMETADATA adding OSSMETADATA for NetflixOSS tracking Dec 11, 2015 update docs to refer to 0.69.0 (#575) Jun 13, 2018
build.gradle update to nebula 5.2.0 (#601) Aug 15, 2018 add --info to release build (#577) Jun 13, 2018 update dependencies (#594) Aug 8, 2018
gradlew update to gradle 4.8 (#567) Jun 5, 2018 add install script Aug 6, 2015
mkdocs.yml docs: add section on `ThreadPoolMonitor` (#464) Sep 2, 2017
settings.gradle add stateless registry for FaaS use-cases (#595) Aug 10, 2018


Simple library for instrumenting code to record dimensional time series.


  • Java 8 or higher.
  • Java 7 or higher for spectator 0.27.x or earlier.



To instrument your code you need to depend on the api library. This provides the minimal interfaces for you to code against and build test cases. The only dependency is slf4j.

If running at Netflix with the standard platform, see the Netflix Integration page on the wiki.

Instrumenting Code

Suppose we have a server and we want to keep track of:

  • Number of requests received with dimensions for breaking down by status code, country, and the exception type if the request fails in an unexpected way.
  • Latency for handling requests.
  • Summary of the response sizes.
  • Current number of active connections on the server.

Here is some sample code that does that:

// In the application initialization setup a registry
Registry registry = new DefaultRegistry();
Server s = new Server(registry);

public class Server {
  private final Registry registry;
  private final Id requestCountId;
  private final Timer requestLatency;
  private final DistributionSummary responseSizes;

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

    // Create a base id for the request count. The id will get refined with
    // additional dimensions when we receive a request.
    requestCountId = registry.createId("server.requestCount");

    // Create a timer for tracking the latency. The reference can be held onto
    // to avoid additional lookup cost in critical paths.
    requestLatency = registry.timer("server.requestLatency");

    // Create a distribution summary meter for tracking the response sizes.
    responseSizes = registry.distributionSummary("server.responseSizes");

    // Gauge type that can be sampled. In this case it will invoke the
    // specified method via reflection to get the value. The registry will
    // keep a weak reference to the object passed in so that registration will
    // not prevent garbage collection of the server object.
    registry.methodValue("server.numConnections", this, "getNumConnections");

  public Response handle(Request req) {
    final long s = System.nanoTime();
    requestLatency.record(() -> {
      try {
        Response res = doSomething(req);

        // Update the counter id with dimensions based on the request. The
        // counter will then be looked up in the registry which should be
        // fairly cheap, such as lookup of id object in a ConcurrentHashMap.
        // However, it is more expensive than having a local variable set
        // to the counter.
        final Id cntId = requestCountId
          .withTag("status", res.status());


        return res;
      } catch (Exception e) {
        final Id cntId = requestCountId
          .withTag("status", "exception")
          .withTag("error", e.getClass().getSimpleName());
        throw e;

  public int getNumConnections() {
    // however we determine the current number of connections on the server