Gathering detailed insights and metrics for datadog-client
Gathering detailed insights and metrics for datadog-client
npm install datadog-client
Typescript
Module System
Min. Node Version
Node Version
NPM Version
72.6
Supply Chain
97.8
Quality
74.5
Maintenance
50
Vulnerability
98.9
License
JavaScript (64.5%)
HTML (35.5%)
Verify real, reachable, and deliverable emails with instant MX records, SMTP checks, and disposable email detection.
Total Downloads
22,593
Last Day
1
Last Week
5
Last Month
45
Last Year
543
105 Stars
260 Commits
45 Forks
2 Watchers
7 Branches
19 Contributors
Updated on Sep 19, 2024
Minified
Minified + Gzipped
Latest Version
3.0.0-alpha.2
Package Id
datadog-client@3.0.0-alpha.2
Unpacked Size
99.36 kB
Size
17.71 kB
File Count
24
NPM Version
6.4.1
Node Version
8.16.1
Cumulative downloads
Total Downloads
Last Day
0%
1
Compared to previous day
Last Week
-68.8%
5
Compared to previous week
Last Month
-21.1%
45
Compared to previous month
Last Year
-16.3%
543
Compared to previous year
Datadog API Node.JS Client :dog2:
:warning: This is a fork from node-dogapi
datadog-client
API Docs: https://omni-tools.github.io/node-datadog-client/dogapi
API Docs: https://brettlangdon.github.io/node-dogapi/dogapi
does not provide any functionality to talk to a local dogstatsd
server.
This library is purely an interface to the HTTP api.
If you are looking for a good Datadog StatsD library, you can check out node-dogstatsd. Or the more adopted hot-shots supporting both StatsD and DogStatsD
1npm install datadog-client
You will need your Datadog api key as well as an application key to use dogapi
.
:closed_lock_with_key: Keys can be found at: https://app.datadoghq.com/account/settings#api
1const dogapi = require('dogapi'); 2 3const options = {api_key: "YOUR_KEY_HERE", app_key: "YOUR_KEY_HERE"}; 4 5dogapi.initialize(options);
If you are behind a proxy you need to a proxy agent. You can use the https proxy agent from http://blog.vanamco.com/proxy-requests-in-node-js/ if you like. To configure dogapi with the agent just add it to the options.
1const dogapi = require('dogapi'); 2 3//Code from http://blog.vanamco.com/proxy-requests-in-node-js/ 4const HttpsProxyAgent = require('./httpsproxyagent'); 5 6const options = { 7 api_key: 'YOUR_KEY_HERE', 8 app_key: 'YOUR_KEY_HERE', 9 proxy_agent: new HttpsProxyAgent({ 10 proxyHost: "MY_PROXY_HOST", 11 proxyPort: 3128 12 }) 13}; 14 15dogapi.initialize(options);
dogapi
now ships with a command line interface dogapi
(or datadog-cli
).
To use it you will need a .dogapirc
file which meets the standards of https://github.com/dominictarr/rc
The config file must contain both api_key
and app_key
keys (you can find your datadog api and app keys here:
https://app.datadoghq.com/account/settings#api
Example:
1{ 2 "api_key": "<API_KEY>", 3 "app_key": "<APP_KEY>" 4}
Please run dogapi --help
to see current usage documentation for the tool.
Every api method available in dogapi
is exposed via the cli tool.
Al major improvements and eventuals breaking changes are TO BE DESCRIBED HERE
We have updated major versions for this library due to a backwards incompatible change to the argument format for dogapi.metric.send
and dogapi.metric.send_all
.
Previously in 1.x.x
:
1dogapi.metric.send('metric.name', 50); 2dogapi.metric.send('metric.name', [datatog.now(), 50]);
Now in 2.x.x
:
1dogapi.metric.send('metric.name', 50); 2dogapi.metric.send('metric.name', [50, 100]); 3dogapi.metric.send('metric.name', [[datadog.now(), 50]]);
Previously in 1.x.x
:
1const metrics = [ 2 {metric: 'metric.name', points: [datadog.now(), 50]}, 3 {metric: 'metric.name', points: 50} 4]; 5dogapi.metric.send_all(metrics);
Now in 2.x.x
:
1const metrics = [ 2 {metric: 'metric.name', points: [[datadog.now(), 50]]}, 3 {metric: 'metric.name', points: [50, 100]}, 4 {metric: 'metric.name', points: 50} 5]; 6dogapi.metric.send_all(metrics);
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
6 existing vulnerabilities detected
Details
Reason
Found 6/23 approved changesets -- score normalized to 2
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
license file not detected
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2025-03-10
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More