Documentation

bigpanda.statusFromLevel() function

bigpanda.statusFromLevel() is a user-contributed function maintained by the package author.

bigpanda.statusFromLevel() converts an alert level to a BigPanda status.

BigPanda accepts one of ok, warning, or critical,.

Function type signature
(level: string) => string

For more information, see Function type signatures.

Parameters

level

(Required) Alert level.

Supported alert levels
Alert levelBigPanda status
critcritical
warnwarning
infook
okok
All other alert levels return a critical BigPanda status.

Examples

Convert an alert level to a BigPanda status

import "contrib/rhajek/bigpanda"

bigpanda.statusFromLevel(level: "crit")// Returns "critical"

Convert alert levels in a stream of tables to BigPanda statuses

Use map() to iterate over rows in a stream of tables and convert alert levels to Big Panda statuses.

import "contrib/rhajek/bigpanda"

data
    |> map(fn: (r) => ({r with big_panda_status: bigpanda.statusFromLevel(level: r._level)}))

View example input and output


Was this page helpful?

Thank you for your feedback!


Telegraf Enterprise now in public beta

Get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

See the Blog Post

The upcoming Telegraf Enterprise offering is for organizations running Telegraf at scale and is comprised of two key components:

  • Telegraf Controller: A control plane (UI + API) that centralizes Telegraf configuration management and agent health visibility.
  • Telegraf Enterprise Support: Official support for Telegraf Controller and Telegraf plugins.

Join the Telegraf Enterprise beta to get early access to the Telegraf Controller and provide feedback to help shape the future of Telegraf Enterprise.

For more information:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On May 27, 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