Skip to content
Commits on Apr 2, 2012
  1. @mbostock

    Disable batchSize on metric queries.

    As best I can tell, this was causing it to return no more than 1,000 results,
    even though the intent was to paginate after the first 1,000. Fishy.
    mbostock committed Apr 2, 2012
Commits on Jan 26, 2012
  1. @mbostock

    Fix off-by-one (or two) in GET metrics.

    Fixes the computation of the expected number of metric values.
    mbostock committed Jan 26, 2012
Commits on Jan 19, 2012
  1. @mbostock

    Merge branch 'fix-error'

    mbostock committed Jan 18, 2012
  2. @mbostock

    Use _id for metrics collections.

    The metrics collections are capped, so an _id is not required. However, starting
    in MongoDB 2.0, you can no longer perform a multi-update without an object _id,
    which caused metrics invalidation to fail. The fix is relatively simple, since
    the metrics values already had an implicit unique id (expression, level, time
    and optional group key): make the id explicit.
    
    Note that this change is not backwards-compatible!
    mbostock committed Jan 18, 2012
Commits on Jan 18, 2012
  1. @mbostock

    Don't fail silently when a string is thrown.

    I'm looking at you, node-mongodb-native. ಠ_ಠ
    mbostock committed Jan 18, 2012
  2. @mbostock

    Merge branch 'metric-get'

    mbostock committed Jan 18, 2012
  3. @mbostock
Commits on Jan 13, 2012
  1. @mbostock

    Allow HTTP GET for metrics.

    You can now issue a simple HTTP GET to retrieve metrics from Cube synchronously,
    rather than fetching metrics asynchronously via WebSockets. The parameters are
    identical to the WebSockets API. So,
    
        {
          "expression": "sum(random)",
          "start": "2012-01-09T01:23:00Z",
          "stop": "2012-01-10T04:56:00Z",
          "step": 300000
        }
    
    Is equivalent to:
    
       http://localhost:1081/1.0/metric
         ?expression=sum(random)
         &start=2012-01-09T01:23:00Z
         &stop=2012-01-10T04:56:00Z
         &step=300000
    
    The results are returned as a JSON array in chronological order. If an error
    occurs, an empty array of results are returned. Fixes #24.
    mbostock committed Jan 13, 2012
  2. @mbostock
Commits on Nov 30, 2011
  1. @mbostock

    Merge branch 'release'

    mbostock committed Nov 30, 2011
  2. @mbostock

    More flexible time intervals.

    You can now specify the metric precision and duration independently, rather than
    being forced to use one of several fixed values.
    mbostock committed Nov 30, 2011
  3. @mbostock

    Add 20-second tier.

    To avoid an explosion of cached metrics for sparse events, we no longer recurse
    all the way to the lowest tier. Instead, we recurse only one level down; if the
    cached metrics are not available at the lower tier, we then jump directly to the
    raw events.
    mbostock committed Nov 30, 2011
  4. @mbostock

    Merge branch 'release'

    mbostock committed Nov 29, 2011
  5. @mbostock
  6. @mbostock

    Updates for Node 0.6.x.

    mbostock committed Nov 29, 2011
Commits on Nov 22, 2011
  1. @mbostock

    Merge branch 'release'

    mbostock committed Nov 22, 2011
  2. @mbostock
  3. @mbostock

    Update D3 to 2.5.2.

    mbostock committed Nov 22, 2011
Commits on Nov 19, 2011
  1. @mbostock
Commits on Nov 18, 2011
  1. @mbostock
  2. @mbostock

    Update D3 to 2.5.1.

    mbostock committed Nov 18, 2011
Commits on Oct 31, 2011
  1. @mbostock

    Add `in` filter.

    mbostock committed Oct 31, 2011
Commits on Oct 15, 2011
  1. @mbostock

    Only close when flushed.

    mbostock committed Oct 14, 2011
Commits on Oct 13, 2011
  1. @mbostock
Commits on Oct 12, 2011
  1. @mbostock
  2. @mbostock

    Merge branch 'release'

    mbostock committed Oct 11, 2011
  3. @mbostock

    Use d3.time.format.iso for date serialization.

    Fixes #2 for Safari 5.0.x and other browsers without toISOString support.
    mbostock committed Oct 11, 2011
Commits on Oct 11, 2011
  1. @mbostock

    Display improvements.

    Fix #5, allowing the y-axis to negative. If only nonpositive values are seen,
    then the y-maximum is 0; if only nonnegative values are seen, then the y-minimum
    is 0; otherwise, the y-domain is the minimum and maximum value. X-labels are
    always drawn on the bottom.
    
    This also adopts D3 2.4's si-prefix format for both y-axis labels and for
    rolling sum values. The y-axis labels use d3.formatPrefix to determine the SI
    prefix that would be used for the largest value, and then applies that to all
    ticks for consistent labeling.
    mbostock committed Oct 11, 2011
Commits on Oct 7, 2011
  1. @mbostock

    Update to D3 2.3.4.

    mbostock committed Oct 7, 2011
  2. @mbostock

    Merge branch 'release'

    mbostock committed Oct 7, 2011
  3. @mbostock
Commits on Oct 5, 2011
  1. @mbostock

    Tweak scaling slightly.

    mbostock committed Oct 5, 2011
  2. @mbostock

    Merge branch 'file-path'

    mbostock committed Oct 5, 2011
  3. @mbostock

    Expose endpoint.

    This allows you to register static files for serving.
    mbostock committed Oct 5, 2011
  4. @mbostock

    Update D3; add more D3 modules.

    This allows you to build custom visualizations hosted by the visualizer.
    mbostock committed Oct 5, 2011
Something went wrong with that request. Please try again.