clients/client-internetmonitor/README.md
AWS SDK for JavaScript InternetMonitor Client for Node.js, Browser and React Native.
<p>Amazon CloudWatch Internet Monitor provides visibility into how internet issues impact the performance and availability between your applications hosted on Amazon Web Services and your end users. It can reduce the time it takes for you to diagnose internet issues from days to minutes. Internet Monitor uses the connectivity data that Amazon Web Services captures from its global networking footprint to calculate a baseline of performance and availability for internet traffic. This is the same data that Amazon Web Services uses to monitor internet uptime and availability. With those measurements as a baseline, Internet Monitor raises awareness for you when there are significant problems for your end users in the different geographic locations where your application runs.</p> <p>Internet Monitor publishes internet measurements to CloudWatch Logs and CloudWatch Metrics, to easily support using CloudWatch tools with health information for geographies and networks specific to your application. Internet Monitor sends health events to Amazon EventBridge so that you can set up notifications. If an issue is caused by the Amazon Web Services network, you also automatically receive an Amazon Web Services Health Dashboard notification with the steps that Amazon Web Services is taking to mitigate the problem.</p> <p>To use Internet Monitor, you create a <i>monitor</i> and associate your application's resources with it - VPCs, NLBs, CloudFront distributions, or WorkSpaces directories - so Internet Monitor can determine where your application's internet traffic is. Internet Monitor then provides internet measurements from Amazon Web Services that are specific to the locations and ASNs (typically, internet service providers or ISPs) that communicate with your application.</p> <p>For more information, see <a href="https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-InternetMonitor.html">Using Amazon CloudWatch Internet Monitor</a> in the <i>Amazon CloudWatch User Guide</i>.</p>To install this package, use the CLI of your favorite package manager:
npm install @aws-sdk/client-internetmonitoryarn add @aws-sdk/client-internetmonitorpnpm add @aws-sdk/client-internetmonitorThe AWS SDK is modulized by clients and commands.
To send a request, you only need to import the InternetMonitorClient and
the commands you need, for example ListMonitorsCommand:
// ES5 example
const { InternetMonitorClient, ListMonitorsCommand } = require("@aws-sdk/client-internetmonitor");
// ES6+ example
import { InternetMonitorClient, ListMonitorsCommand } from "@aws-sdk/client-internetmonitor";
To send a request:
send operation on the client, providing the command object as input.const client = new InternetMonitorClient({ region: "REGION" });
const params = { /** input parameters */ };
const command = new ListMonitorsCommand(params);
We recommend using the await operator to wait for the promise returned by send operation as follows:
// async/await.
try {
const data = await client.send(command);
// process data.
} catch (error) {
// error handling.
} finally {
// finally.
}
You can also use Promise chaining.
client
.send(command)
.then((data) => {
// process data.
})
.catch((error) => {
// error handling.
})
.finally(() => {
// finally.
});
The aggregated client class is exported from the same package, but without the "Client" suffix.
InternetMonitor extends InternetMonitorClient and additionally supports all operations, waiters, and paginators as methods.
This style may be familiar to you from the AWS SDK for JavaScript v2.
If you are bundling the AWS SDK, we recommend using only the bare-bones client (InternetMonitorClient).
More details are in the blog post on
modular packages in AWS SDK for JavaScript.
import { InternetMonitor } from "@aws-sdk/client-internetmonitor";
const client = new InternetMonitor({ region: "REGION" });
// async/await.
try {
const data = await client.listMonitors(params);
// process data.
} catch (error) {
// error handling.
}
// Promises.
client
.listMonitors(params)
.then((data) => {
// process data.
})
.catch((error) => {
// error handling.
});
// callbacks (not recommended).
client.listMonitors(params, (err, data) => {
// process err and data.
});
When the service returns an exception, the error will include the exception information, as well as response metadata (e.g. request id).
try {
const data = await client.send(command);
// process data.
} catch (error) {
const { requestId, cfId, extendedRequestId } = error.$metadata;
console.log({ requestId, cfId, extendedRequestId });
/**
* The keys within exceptions are also parsed.
* You can access them by specifying exception names:
* if (error.name === 'SomeServiceException') {
* const value = error.specialKeyInException;
* }
*/
}
See also docs/ERROR_HANDLING.
Please use these community resources for getting help. We use GitHub issues for tracking bugs and feature requests, but have limited bandwidth to address them.
aws-sdk-js
on AWS Developer Blog.aws-sdk-js.To test your universal JavaScript code in Node.js, browser and react-native environments, visit our code samples repo.
This client code is generated automatically. Any modifications will be overwritten the next time the @aws-sdk/client-internetmonitor package is updated.
To contribute to client you can check our generate clients scripts.
This SDK is distributed under the Apache License, Version 2.0, see LICENSE for more information.
Command API Reference / Input / Output
</details> <details> <summary> DeleteMonitor </summary>Command API Reference / Input / Output
</details> <details> <summary> GetHealthEvent </summary>Command API Reference / Input / Output
</details> <details> <summary> GetInternetEvent </summary>Command API Reference / Input / Output
</details> <details> <summary> GetMonitor </summary>Command API Reference / Input / Output
</details> <details> <summary> GetQueryResults </summary>Command API Reference / Input / Output
</details> <details> <summary> GetQueryStatus </summary>Command API Reference / Input / Output
</details> <details> <summary> ListHealthEvents </summary>Command API Reference / Input / Output
</details> <details> <summary> ListInternetEvents </summary>Command API Reference / Input / Output
</details> <details> <summary> ListMonitors </summary>Command API Reference / Input / Output
</details> <details> <summary> ListTagsForResource </summary>Command API Reference / Input / Output
</details> <details> <summary> StartQuery </summary>Command API Reference / Input / Output
</details> <details> <summary> StopQuery </summary>Command API Reference / Input / Output
</details> <details> <summary> TagResource </summary>Command API Reference / Input / Output
</details> <details> <summary> UntagResource </summary> </details> <details> <summary> UpdateMonitor </summary> </details>