Comparing version 1.1.2 to 1.1.3
{ | ||
"name": "cubed", | ||
"version": "1.1.2", | ||
"version": "1.1.3", | ||
"description": "A udp-based, cube backend for statsd", | ||
@@ -27,2 +27,2 @@ "main": "index.js", | ||
"readmeFilename": "README.md" | ||
} | ||
} |
@@ -1,4 +0,6 @@ | ||
cubed | ||
===== | ||
DEPRECATED: cubed | ||
================= | ||
**This module has been deprecated as of November 9, 2015. It will be removed from npm on November 1, 2016.** | ||
A udp-based, [cube](https://github.com/square/cube) backend for [statsd](https://github.com/etsy/statsd) | ||
@@ -15,3 +17,3 @@ | ||
Add the `cubed` backend configuration to your statsd configuration file. | ||
Add the `cubed` backend configuration to your statsd configuration file. | ||
@@ -101,3 +103,3 @@ ```javascript | ||
## namespacing statsd -> cube | ||
## namespacing statsd → cube | ||
@@ -121,10 +123,1 @@ in statsd, periods are used to namespace events. unfortunately, cube [does not (yet) support periods](https://github.com/square/cube/issues/95) in event names though they are [valid collection names](http://docs.mongodb.org/manual/faq/developers/). (hopefully this is patched soon...) | ||
cubed uses udp to communicate with the cube instance. although tcp is supported by cube, it is not supported by statsd. statsd is designed to be "fire and forget". so too is cubed. if you are looking for guaranteed data persistence, consider using cube's tcp interface directly rather than through statsd and cubed. | ||
## why cubed | ||
the future of cube and statsd is uncertain. indeed, that is the fate of all software. however, at present, our team has found the cube evaluator to be one of the more robust options available--after you master the slightly unusual [metric expression syntax](https://github.com/square/cube/wiki/Queries#wiki-metric). | ||
in addition, the recent [infochimps merge](https://github.com/square/cube/pull/129) into `cube/master` has only increased our appreciation for cube and its maintainers. statsd is, as advertised, both fast and robust for bursted statistical analysis. they are both also rediculously easy to integrate into node applications or any udp-enabled service. | ||
graphite (which uses carbon) is an incredibly powerful solution. however, the ui and authorization strategies need some tlc. installing graphite is a bit rough-and-tumble and an adventure in python package dependencies. |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
0
8882
121