Documentation

pagerduty.sendEvent() function

pagerduty.sendEvent() sends an event to PagerDuty and returns the HTTP response code of the request.

Function type signature
(  class: A,  client: B,  clientURL: C,  dedupKey: D,  eventAction: E,  group: F,  routingKey: G,  severity: H,  source: I,  summary: string,  timestamp: J,  ?component: K,  ?customDetails: L,  ?pagerdutyURL: string, ) => int where L: Equatable

For more information, see Function type signatures.

Parameters

pagerdutyURL

PagerDuty endpoint URL.

Default is https://events.pagerduty.com/v2/enqueue.

routingKey

(Required) Routing key generated from your PagerDuty integration.

client

(Required) Name of the client sending the alert.

clientURL

(Required) URL of the client sending the alert.

dedupKey

(Required) Per-alert ID that acts as deduplication key and allows you to acknowledge or change the severity of previous messages. Supports a maximum of 255 characters.

class

(Required) Class or type of the event.

Classes are user-defined. For example, ping failure or cpu load.

group

(Required) Logical grouping used by PagerDuty.

Groups are user-defined. For example, app-stack.

severity

(Required) Severity of the event.

Valid values:

  • critical
  • error
  • warning
  • info

eventAction

(Required) Event type to send to PagerDuty.

Valid values:

  • trigger
  • resolve
  • acknowledge

source

(Required) Unique location of the affected system. For example, the hostname or fully qualified domain name (FQDN).

component

Component responsible for the event.

summary

(Required) Brief text summary of the event used as the summaries or titles of associated alerts. The maximum permitted length is 1024 characters.

timestamp

(Required) Time the detected event occurred in RFC3339nano format.

customDetails

Record with additional details about the event.

Examples

Send an event to PagerDuty

import "pagerduty" import "pagerduty"  pagerduty.sendEvent(  routingKey: "example-routing-key",  client: "example-client",  clientURL: "http://example-url.com",  dedupKey: "example-dedup-key",  class: "example-class",  eventAction: "trigger",  group: "example-group",  severity: "crit",  component: "example-component",  source: "example-source",  summary: "example-summary",  timestamp: now(),  customDetails: {"example-key": "example value"}, )

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2