Live Platform
  • Introduction
  • Release Notes
    • Live 3
      • 3.59.0
      • 3.58.0
      • 3.57.0
      • 3.56.0
      • 3.55.0
      • 3.54.0
      • 3.53.0
      • 3.52.0
      • 3.51.0
      • 3.50.0
      • 3.49.0
      • 3.48.0
      • 3.47.0
      • 3.46.0
      • 3.45.0
      • 3.44.0
      • 3.43.0
      • 3.42.0
      • 3.41.0
      • 3.40.0
      • 3.39.0
      • 3.38.0
      • 3.37.0
      • 3.36.0
      • 3.35.0
      • 3.34.0
      • 3.33.0
      • 3.32.0
      • 3.31.0
      • 3.30.0
      • 3.29.0
      • 3.28.0
      • 3.27.0
      • 3.26.0
      • 3.25.0
      • 3.24.0
      • 3.23.0
      • 3.22.0
      • 3.21.0
      • 3.20.0
      • 3.19.0
      • 3.18.0
      • 3.17.0
      • 3.16.0
      • 3.15.0
      • 3.14.0
      • 3.13.0
      • 3.12.0
      • 3.11.0
      • 3.10.0
      • 3.9.0
      • 3.8.0
      • 3.7.0
      • 3.6.0
      • 3.5.0
      • 3.4.0
      • 3.3.0
      • 3.2.0
      • 3.1.0
      • 3.0.0
    • Live 2
  • Articles
    • Creating an aggregation
    • Creating a pipe
  • Theoretical Background
    • Fundamentals
    • Key Advantages
  • Platform Architecture
    • Introduction
    • Queries
    • Glossary
  • Featured plugins
    • Annotations
    • Groovy support
    • Messenger
    • Microsoft Teams
    • MongoDB
    • MongoDB Timeseries
    • MongoDB Kit
    • Purge plugin
    • SQL
    • TCP Input
    • TimescaleDB
  • Data visualization
    • Pipes widgets
      • Temporal
      • Cartesian
      • Multi-value snapshot
      • Single-value snapshot
      • Tables
      • Heatmap
      • JSX Widgets
      • Lollipop
      • Histogram
      • State Timeline
      • Boxplot
    • Pipes modifiers on Pipes charts
  • Alerts and notifications
    • Pipes modifiers on rules
  • Pipes Queries
    • Introduction
    • Dynamic filters
    • Meta parameters
    • Reducer
      • Uniform compress
      • PIP
    • Storage Hints
    • Execution Context
    • Event flow modifiers
  • Developers
    • Plugins
    • Packages
    • Backend API
      • Lookup Tables
      • Extensions
      • Settings
      • Storage Providers
      • Web Services
      • Web Setup
      • Entity Audit
    • Web application
      • Services
        • Point service
        • Menu service
      • Browser Compatibility
      • Runtime modules
        • Core Javascript modules
        • Library modules
        • Adding modules to runtime
      • Localization (i18n)
      • Date formatting
      • Dashboard and Widgets
        • Widget API
        • Custom widget editors
        • Live Event Types
        • Live Widget Configuration
        • Live Widget Packaging
        • Widget Request Interceptors
      • React Contexts
        • Dashboard
        • Dashboard widget
      • Registering Home Page options
    • Python application
    • Subscribing to Live Events
  • Administration
    • Configuration
      • Home Page Customization
      • live.properties
    • Infrastructure Monitoring
    • Storage Monitoring
    • Queries Monitoring
    • Logs Monitoring
    • Data Purging
  • Features
    • Access Permission
    • Datasources
    • Export Dashboard
    • Partial Indexes
    • WebApp Metrics
    • Entity Audit
Powered by GitBook
On this page

Was this helpful?

  1. Data visualization

Pipes modifiers on Pipes charts

PreviousBoxplotNextPipes modifiers on rules

Last updated 3 years ago

Was this helpful?

Standard charts listen to Pipes modifiers.

Some modifiers are available as and some are available as simple variables on the event itself (starting with __).

Property

Type

Supported charts

Default

Since

@meta.color or __color

string or map

temporal, cartesian, bar, column, funnel, pie, value

@meta on 2.25.2

@meta.dashStyle or __dashStyle

string

temporal, cartesian

@meta on 2.25.2

@meta.lineWidth or __lineWidth

integer

temporal, cartesian

@meta on 2.25.2

__markerRadius

integer

temporal, cartesian

__markerEnabled

boolean

temporal, cartesian

__markerSymbol

string

temporal, cartesian

__dataLabelEnabled

boolean

temporal, cartesian

__description

string

temporal, cartesian

__wstart

long

temporal

__xAxisMin

long

cartesian

__xAxisMax

long

cartesian

__clear

boolean or map

temporal, cartesian

__syncTooltipField

string

temporal, cartesian

2.15.3

__formatted

string or map

temporal, cartesian, bar, column, funnel, pie

2.17.0

__columnWidth

integer

ranking, feed

2.19.3

__uid

string

feed

2.20.6

__title

string

temporal, cartesian

3.9.0

@meta.color

map

temporal, cartesian

2.25.2

@meta.enableDataGapsReport

boolean

temporal

2.28.0

@meta.dataGapsReportThreshold

long

temporal

60000

2.28.0

@meta.zIndex

map

temporal, cartesian

2.25.2

@meta.zones

map<seq<obj>>

temporal, cartesian

2.25.2

@meta.legendIndex

map

temporal, cartesian

2.25.2

@meta.hideInLegend

string or map

temporal, cartesian

2.25.2

@meta.disableStateMarker

boolean

temporal, cartesian

2.25.8

@meta.disableMouseTracking

boolean

temporal, cartesian

2.25.2

@meta.lineColor

string

temporal, cartesian

2.25.2

@meta.zoneAxis

x or y

temporal, cartesian

2.25.2

@meta.polygon

map

cartesian

2.25.2

@meta.yAxis

seq<map>

temporal, cartesian

2.27.0

@meta.chartOptions

temporal, cartesian, column, bar, gauge, funnel, pie

@meta.legendIndex

map(name, order)

temporal, cartesian, column, bar, gauge, funnel, pie

The @meta parameters must be used on the body of a query, for example => @meta value as property.

@meta modifiers can be set globally or individually.

=> @meta "red" as colorwill make all series red.=> @meta newmap("my-series-name", "red") as color will make "my-series-name" red.

Examples

@meta.yAxis

Defines the y axes configurations for the chart.

=> 
  @meta (
    newmap(
      "label", "a",
      "color", "red", 
      "min", 20,
      "max", "auto",
      "position", "right",
      "uom", "m",
      "fields", ("a"):seq
    ),
    newmap(
      "label", "b",
      "color", "blue", 
      -- "min", 100,
      "max", 200,
      "position", "right",
      "uom", "m",
      "fields", ("b"):seq
    ),
  ):seq as yAxis

event.__formatted

A formatted string that will be used to display the field value.

@set newmap("a", "$ 56.87") as __formatted

@meta.zIndex

Changes series zIndex, use in case you want to a make a field overlap another.

=> @meta newmap("a", 1, "b", 2) as zIndex

@meta.hideInLegend

Changes hide selected series on the chart legend.

=> @meta newmap("a", true) as hideInLegend
=> @meta newmap("a", true, "b", true) as hideInLegend
=> @meta true as hideInLegend -- hide all legends

@meta.zones

Create value thresholds that defines a new color for the field above that value.

=> @meta newmap(
    "a", 
    (newmap(
        "color", "green",
        "value", 0.5
    )
    ):seq) as zones
    
-- for the field "a" above value 0.5, field should be color "green"

@meta.color

Changes a field color

=> @meta newmap("a", "red", "b", "blue") as color

@meta.lineWidth

Defines the line width for the selected series.

=> @meta newmap("a", 1, "b", 2) as lineWidth
=> @meta 4 as lineWidth -- apply to all series

@meta.legendIndex

Defines the legend and tooltip order on charts

=> @meta newmap("series-a", 1, "series-b", 2) as legendIndex

@meta.dashStyle

Changes the default dash (Solid) style for series.

=> @meta newmap("a", 'Dash') as dashStyle
=> @meta 'Dash' as dashStyle -- apply to all series

Accepted dashStyle values:

  • Solid

  • Dash (DashDot)

  • Dot

  • LongDash (LongDashDot, LongDashDotDot)

  • ShortDash (ShortDashDot, ShortDashDotDot)

  • ShortDot

@meta.polygon

=> @meta 
    newmap(
        "color", "rgba(255, 0, 0, 0.3)", 
        "points", "[[1, 2], [2, 3], [4, 3]]"$:jsonparse()
    ) as polygon

@meta.enableDataGapsReport and @meta.dataGapsReportThreshold

This query generates the chart in the image below.

=> sin(otimestamp() / pi() / 36000) as r, (ostart():dateformat('mm')#) as min every second
=> @filter min % 3 != 0
=> r
=> @meta true as enableDataGapsReport, 61000 as dataGapsReportThreshold

map ()

meta parameters
ref
Data gaps demonstration