zenoss.event() function

zenoss.event() is a user-contributed function maintained by the package author.

zenoss.event() sends an event to Zenoss.

Function type signature
    severity: A,
    url: string,
    ?action: B,
    ?apiKey: C,
    ?collector: D,
    ?component: E,
    ?device: F,
    ?eventClass: G,
    ?eventClassKey: H,
    ?message: I,
    ?method: J,
    ?password: string,
    ?summary: K,
    ?tid: L,
    ?type: M,
    ?username: string,
) => int where C: Equatable
For more information, see Function type signatures.



(Required) Zenoss router endpoint URL.


Zenoss username to use for HTTP BASIC authentication. Default is "" (no authentication).


Zenoss password to use for HTTP BASIC authentication. Default is "" (no authentication).


Zenoss cloud API key. Default is "" (no API key).


Zenoss router name. Default is “EventsRouter”.


EventsRouter method. Default is “add_event”.


Event type. Default is “rpc”.


Temporary request transaction ID. Default is 1.


Event summary. Default is "".


Related device. Default is "".


Related component. Default is "".


(Required) Event severity level.

Supported values:

  • Critical
  • Warning
  • Info
  • Clear


Event class. Default is "".


Event class key. Default is "".


Zenoss collector. Default is "".


Related message. Default is "".


Send the last reported value and severity to Zenoss

import "contrib/bonitoo-io/zenoss"
import "influxdata/influxdb/secrets"

username = secrets.get(key: "ZENOSS_USERNAME")
password = secrets.get(key: "ZENOSS_PASSWORD")

lastReported =
    from(bucket: "example-bucket")
        |> range(start: -1m)
        |> filter(fn: (r) => r._measurement == "cpu" and r._field == "usage_idle")
        |> last()
        |> findRecord(fn: (key) => true, idx: 0)

    url: "",
    username: username,
    username: password,
    component: "CPU",
    eventClass: "/App",
        if lastReported._value < 1.0 then
        else if lastReported._value < 5.0 then
        else if lastReported._value < 20.0 then

Was this page helpful?

Thank you for your feedback!

Introducing InfluxDB Clustered

A highly available InfluxDB 3.0 cluster on your own infrastructure.

InfluxDB Clustered is a highly available InfluxDB 3.0 cluster built for high write and query workloads on your own infrastructure.

InfluxDB Clustered is currently in limited availability and is only available to a limited group of InfluxData customers. If interested in being part of the limited access group, please contact the InfluxData Sales team.

Learn more
Contact InfluxData Sales

The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following:

State of the InfluxDB Cloud Serverless documentation

InfluxDB Cloud Serverless documentation is a work in progress.

The new documentation for InfluxDB Cloud Serverless is a work in progress. We are adding new information and content almost daily. Thank you for your patience!

If there is specific information you’re looking for, please submit a documentation issue.