Documentation

opsgenie.endpoint() function

opsgenie.endpoint() is a user-contributed function maintained by the package author.

opsgenie.endpoint() sends an alert message to Opsgenie using data from table rows.

Usage

opsgenie.endpoint is a factory function that outputs another function. The output function requires a mapFn parameter.

mapFn

A 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 fields:

  • message
  • alias
  • description
  • priority
  • responders
  • tags
  • actions
  • details
  • visibleTo

For more information, see opsgenie.sendAlert.

Function type signature
(  apiKey: string,  ?entity: string,  ?url: string, ) => (  mapFn: (  r: A,  ) => {  B with  visibleTo: [string],  tags: E,  responders: [string],  priority: string,  message: string,  details: D,  description: string,  alias: string,  actions: C,  }, ) => (<-tables: stream[A]) => stream[{A with _sent: string}] where D: Stringable

For more information, see Function type signatures.

Parameters

url

Opsgenie API URL. Defaults to https://api.opsgenie.com/v2/alerts.

apiKey

(Required) (Required) Opsgenie API authorization key.

entity

Alert entity used to specify the alert domain.

Examples

Send critical statuses to Opsgenie

import "influxdata/influxdb/secrets" import "contrib/sranka/opsgenie"  apiKey = secrets.get(key: "OPSGENIE_APIKEY") endpoint = opsgenie.endpoint(apiKey: apiKey)  crit_statuses =  from(bucket: "example-bucket")  |> range(start: -1m)  |> filter(fn: (r) => r._measurement == "statuses" and status == "crit")  crit_statuses  |> endpoint(  mapFn: (r) =>  ({  message: "Great Scott!- Disk usage is: ${r.status}.",  alias: "disk-usage-${r.status}",  description: "",  priority: "P3",  responders: ["user:john@example.com", "team:itcrowd"],  tags: [],  entity: "my-lab",  actions: [],  details: "{}",  visibleTo: [],  }),  )()

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.7

Key enhancements in InfluxDB 3.7 and the InfluxDB 3 Explorer 1.5.

See the Blog Post

InfluxDB 3.7 is now available for both Core and Enterprise, landing alongside version 1.5 of the InfluxDB 3 Explorer UI. This release focuses on giving developers faster visibility into what their system is doing with one-click monitoring, a streamlined installation pathway, and broader updates that simplify day-to-day operations.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On February 3, 2026, 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