Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

NetworkMonitor

import { NetworkMonitor } from "https://aws-api-bqtgftz736ft.deno.dev/v0.5/services/networkmonitor.ts?docs=full";
class NetworkMonitor {
constructor(apiFactory: client.ApiFactory);
async createMonitor(params: CreateMonitorInput, opts?: client.RequestOptions): Promise<CreateMonitorOutput>;
async createProbe(params: CreateProbeInput, opts?: client.RequestOptions): Promise<CreateProbeOutput>;
async deleteMonitor(params: DeleteMonitorInput, opts?: client.RequestOptions): Promise<void>;
async deleteProbe(params: DeleteProbeInput, opts?: client.RequestOptions): Promise<void>;
async getMonitor(params: GetMonitorInput, opts?: client.RequestOptions): Promise<GetMonitorOutput>;
async getProbe(params: GetProbeInput, opts?: client.RequestOptions): Promise<GetProbeOutput>;
async listMonitors(params?: ListMonitorsInput, opts?: client.RequestOptions): Promise<ListMonitorsOutput>;
async listTagsForResource(params: ListTagsForResourceInput, opts?: client.RequestOptions): Promise<ListTagsForResourceOutput>;
async tagResource(params: TagResourceInput, opts?: client.RequestOptions): Promise<void>;
async untagResource(params: UntagResourceInput, opts?: client.RequestOptions): Promise<void>;
async updateMonitor(params: UpdateMonitorInput, opts?: client.RequestOptions): Promise<UpdateMonitorOutput>;
async updateProbe(params: UpdateProbeInput, opts?: client.RequestOptions): Promise<UpdateProbeOutput>;
 
static ApiMetadata: client.ApiMetadata;
}

§Constructors

§
new NetworkMonitor(apiFactory: client.ApiFactory)
[src]

§Methods

§
createMonitor(params: CreateMonitorInput, opts?: client.RequestOptions): Promise<CreateMonitorOutput>
[src]

Creates a monitor between a source subnet and destination IP address. Within a monitor you'll create one or more probes that monitor network traffic between your source Amazon Web Services VPC subnets and your destination IP addresses. Each probe then aggregates and sends metrics to Amazon CloudWatch.

You can also create a monitor with probes using this command. For each probe, you define the following:

  • source—The subnet IDs where the probes will be created.
  • destination— The target destination IP address for the probe.
  • destinationPort—Required only if the protocol is TCP.
  • protocol—The communication protocol between the source and destination. This will be either TCP or ICMP.
  • packetSize—The size of the packets. This must be a number between 56 and 8500.
  • (Optional) tags —Key-value pairs created and assigned to the probe.
§
createProbe(params: CreateProbeInput, opts?: client.RequestOptions): Promise<CreateProbeOutput>
[src]

Create a probe within a monitor. Once you create a probe, and it begins monitoring your network traffic, you'll incur billing charges for that probe. This action requires the monitorName parameter. Run ListMonitors to get a list of monitor names. Note the name of the monitorName you want to create the probe for.

§
deleteMonitor(params: DeleteMonitorInput, opts?: client.RequestOptions): Promise<void>
[src]

Deletes a specified monitor.

This action requires the monitorName parameter. Run ListMonitors to get a list of monitor names.

§
deleteProbe(params: DeleteProbeInput, opts?: client.RequestOptions): Promise<void>
[src]

Deletes the specified probe. Once a probe is deleted you'll no longer incur any billing fees for that probe.

This action requires both the monitorName and probeId parameters. Run ListMonitors to get a list of monitor names. Run GetMonitor to get a list of probes and probe IDs. You can only delete a single probe at a time using this action.

§
getMonitor(params: GetMonitorInput, opts?: client.RequestOptions): Promise<GetMonitorOutput>
[src]

Returns details about a specific monitor.

This action requires the monitorName parameter. Run ListMonitors to get a list of monitor names.

§
getProbe(params: GetProbeInput, opts?: client.RequestOptions): Promise<GetProbeOutput>
[src]

Returns the details about a probe. This action requires both the monitorName and probeId parameters. Run ListMonitors to get a list of monitor names. Run GetMonitor to get a list of probes and probe IDs.

§
listMonitors(params?: ListMonitorsInput, opts?: client.RequestOptions): Promise<ListMonitorsOutput>
[src]

Returns a list of all of your monitors.

§

Lists the tags assigned to this resource.

§
tagResource(params: TagResourceInput, opts?: client.RequestOptions): Promise<void>
[src]

Adds key-value pairs to a monitor or probe.

§
untagResource(params: UntagResourceInput, opts?: client.RequestOptions): Promise<void>
[src]

Removes a key-value pair from a monitor or probe.

§
updateMonitor(params: UpdateMonitorInput, opts?: client.RequestOptions): Promise<UpdateMonitorOutput>
[src]

Updates the aggregationPeriod for a monitor. Monitors support an aggregationPeriod of either 30 or 60 seconds. This action requires the monitorName and probeId parameter. Run ListMonitors to get a list of monitor names.

§
updateProbe(params: UpdateProbeInput, opts?: client.RequestOptions): Promise<UpdateProbeOutput>
[src]

Updates a monitor probe. This action requires both the monitorName and probeId parameters. Run ListMonitors to get a list of monitor names. Run GetMonitor to get a list of probes and probe IDs.

You can update the following para create a monitor with probes using this command. For each probe, you define the following:

  • state—The state of the probe.
  • destination— The target destination IP address for the probe.
  • destinationPort—Required only if the protocol is TCP.
  • protocol—The communication protocol between the source and destination. This will be either TCP or ICMP.
  • packetSize—The size of the packets. This must be a number between 56 and 8500.
  • (Optional) tags —Key-value pairs created and assigned to the probe.

§Static Properties