arbor-monad-metric-datadog: Metric library backend for datadog.
This is a package candidate release! Here you can preview how this package release will appear once published to the main package index (which can be accomplished via the 'maintain' link below). Please note that once a package has been published to the main package index it cannot be undone! Please consult the package uploading documentation for more information.
Please see the README on Github at https://github.com/arbor/arbor-monad-metric-datadog#readme
[Skip to Readme]
Properties
| Versions | 0.0.1, 0.0.3, 1.0.0, 1.0.0, 1.1.0, 1.1.1, 1.1.2 |
|---|---|
| Change log | ChangeLog.md |
| Dependencies | arbor-datadog (>=0.0.0 && <0.1), arbor-monad-metric (>=1.1.0 && <1.2), base (>=4.7 && <5), bytestring (>=0.10.8 && <0.11), containers (>=0.5.10 && <0.6), generic-lens (>=1.0.0.2 && <1.2), lens (>=4.16 && <4.18), mtl (>=2.2.2 && <2.3), network (>=2.6.0 && <2.9), resourcet (>=1.2.1 && <1.3), stm (>=2.4.0 && <2.6), text (>=1.2.3 && <1.3), transformers (>=0.5.2 && <0.6) [details] |
| License | MIT |
| Copyright | Arbor Networks |
| Author | Arbor Networks |
| Maintainer | mayhem@arbor.net |
| Category | Metrics |
| Home page | https://github.com/arbor/arbor-monad-metric-datadog#readme |
| Bug tracker | https://github.com/arbor/arbor-monad-metric-datadog/issues |
| Source repo | head: git clone https://github.com/arbor/arbor-monad-metric-datadog |
| Uploaded | by arbornetworks at 2018-12-06T00:59:53Z |
Modules
[Index] [Quick Jump]
Downloads
- arbor-monad-metric-datadog-1.0.0.tar.gz [browse] (Cabal source package)
- Package description (as included in the package)
Maintainer's Corner
Package maintainers
For package maintainers and hackage trustees
Readme for arbor-monad-metric-datadog-1.0.0
[back to package description]arbor-monad-metric-datadog
This is a fork of arbor-monad-counter-datadog into a module namespace to add support for varied metric types.
The arbor-monad-counter-datadog library is retained for backwards compatibility.
Release
Bump the version in the *.cabal version; create a new commit “New version x.x.x.x`, wait for tagged build in CI and find a link to hackage in the build output and open it. Log in with hackage credentials if necessary, then click “publish candidate”