Stackdriver Monitoring: Node.js Client
Stackdriver Monitoring collects metrics, events, and metadata from Google Cloud Platform, Amazon Web Services (AWS), hosted uptime probes, application instrumentation, and a variety of common application components including Cassandra, Nginx, Apache Web Server, Elasticsearch and many others.
A comprehensive list of changes in each version may be found in the CHANGELOG.
- Stackdriver Monitoring Node.js Client API Reference
- Stackdriver Monitoring Documentation
- github.com/googleapis/nodejs-monitoring
Read more about the client libraries for Cloud APIs, including the older Google APIs Client Libraries, in Client Libraries Explained.
Table of contents:
Quickstart
Before you begin
- Select or create a Cloud Platform project.
- Enable billing for your project.
- Enable the Stackdriver Monitoring API.
- Set up authentication with a service account so you can access the API from your local workstation.
Installing the client library
npm install @google-cloud/monitoring
Using the client library
// Imports the Google Cloud client library
const monitoring = require('@google-cloud/monitoring');
async function quickstart() {
// Creates a client
const client = new monitoring.MetricServiceClient();
// TODO(developer): Uncomment and set the following variables
// const projectId = "PROJECT_ID"
// Prepares an individual data point
const dataPoint = {
interval: {
endTime: {
seconds: Date.now() / 1000,
},
},
value: {
// The amount of sales
doubleValue: 123.45,
},
};
// Prepares the time series request
const request = {
name: client.projectPath(projectId),
timeSeries: [
{
// Ties the data point to a custom metric
metric: {
type: 'custom.googleapis.com/stores/daily_sales',
labels: {
store_id: 'Pittsburgh',
},
},
resource: {
type: 'global',
labels: {
project_id: projectId,
},
},
points: [dataPoint],
},
],
};
// Writes time series data
const [result] = await client.createTimeSeries(request);
console.log('Done writing time series data.', result);
}
quickstart();
Samples
Samples are in the samples/
directory. Each sample's README.md
has instructions for running its sample.
Sample | Source Code | Try it |
---|---|---|
Alerts.backup Policies | source code | |
Alerts.delete Channels | source code | |
Alerts.enable Policies | source code | |
Alerts.list Policies | source code | |
Alerts.replace Channels | source code | |
Alerts.restore Policies | source code | |
Create Metric Descriptor | source code | |
Delete Metric Descriptor | source code | |
Get Metric Descriptor | source code | |
Get Monitored Resource Descriptor | source code | |
List Metric Descriptors | source code | |
List Monitored Resource Descriptors | source code | |
Read Time Series Aggregate | source code | |
Read Time Series Data | source code | |
Read Time Series Fields | source code | |
Read Time Series Reduce | source code | |
Write Time Series Data | source code | |
Quickstart | source code | |
Uptime | source code |
The Stackdriver Monitoring Node.js Client API Reference documentation also contains samples.
Supported Node.js Versions
Our client libraries follow the Node.js release schedule. Libraries are compatible with all current active and maintenance versions of Node.js. If you are using an end-of-life version of Node.js, we recommend that you update as soon as possible to an actively supported LTS version.
Google's client libraries support legacy versions of Node.js runtimes on a best-efforts basis with the following warnings:
- Legacy versions are not tested in continuous integration.
- Some security patches and features cannot be backported.
- Dependencies cannot be kept up-to-date.
Client libraries targeting some end-of-life versions of Node.js are available, and
can be installed through npm dist-tags.
The dist-tags follow the naming convention legacy-(version)
.
For example, npm install @google-cloud/monitoring@legacy-8
installs client libraries
for versions compatible with Node.js 8.
Versioning
This library follows Semantic Versioning.
This library is considered to be stable. The code surface will not change in backwards-incompatible ways unless absolutely necessary (e.g. because of critical security issues) or with an extensive deprecation period. Issues and requests against stable libraries are addressed with the highest priority.
More Information: Google Cloud Platform Launch Stages
Contributing
Contributions welcome! See the Contributing Guide.
Please note that this README.md
, the samples/README.md
,
and a variety of configuration files in this repository (including .nycrc
and tsconfig.json
)
are generated from a central template. To edit one of these files, make an edit
to its templates in
directory.
License
Apache Version 2.0
See LICENSE