Documentation

pagerduty.endpoint() function

pagerduty.endpoint() returns a function that sends a message to PagerDuty that includes output data.

Usage

pagerduty.endpoint() is a factory function that outputs another function. The output function requires a mapFn parameter.

mapFn

Function that builds the record used to generate the POST request. Requires an r parameter.

mapFn accepts a table row (r) and returns a record that must include the following properties:

  • routingKey
  • client
  • client_url
  • class
  • eventAction
  • group
  • severity
  • source
  • component
  • summary
  • timestamp
  • customDetails
Function type signature
(  ?url: string, ) => (  mapFn: (  r: {A with _pagerdutyDedupKey: string},  ) => {  B with  timestamp: K,  summary: string,  source: J,  severity: I,  routingKey: H,  group: G,  eventAction: F,  clientURL: E,  client: D,  class: C,  }, ) => (<-tables: stream[A]) => stream[{A with _status: string, _sent: string, _pagerdutyDedupKey: string, _body: string}]

For more information, see Function type signatures.

Parameters

url

PagerDuty v2 Events API URL.

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

Examples

Send critical statuses to a PagerDuty endpoint

import "pagerduty" import "influxdata/influxdb/secrets"  routingKey = secrets.get(key: "PAGERDUTY_ROUTING_KEY") toPagerDuty = pagerduty.endpoint()  crit_statuses =  from(bucket: "example-bucket")  |> range(start: -1m)  |> filter(fn: (r) => r._measurement == "statuses" and r.status == "crit")  crit_statuses  |> toPagerDuty(  mapFn: (r) =>  ({r with  routingKey: routingKey,  client: r.client,  clientURL: r.clientURL,  class: r.class,  eventAction: r.eventAction,  group: r.group,  severity: r.severity,  source: r.source,  component: r.component,  summary: r.summary,  timestamp: r._time,  customDetails: {"ping time": r.ping, load: r.load},  }),  )()

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