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!


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