SQL window functions
InfluxDB 3 Enterprise is in public beta and available for testing and feedback,
but is not meant for production use yet.
Both the product and this documentation are works in progress.
We welcome and encourage your input about your experience with the beta and
invite you to join our public channels for updates and to
share feedback.
Beta expectations and recommendations
- No more breaking changes
While in beta, we will no longer make breaking changes to the
InfluxDB 3 Enterprise API. Any updates to file formats or organization
will have in-place upgrade paths for beta builds. Use the Beta
for testing and validation purposes, knowing that when you upgrade,
your data will come with it, and your APIs will all work the same. - Weekly releases
While in beta, we’ll be making weekly InfluxDB 3 Enterprise releases
and providing release notes to make it easy to track updates. - Processing engine is still in alpha
The embedded Python VM that is the processing engine should still
be considered alpha software. It is fully functional and allows
users to create and share plugins that trigger off of writes, a
schedule, or requests to an HTTP endpoint. However, we want to
continue iterating on user feedback and making changes where they
make sense. While we don't anticipate any breaking changes,
we're not yet committed to the current API as the long term
support target. Feedback we get during this phase will be important
to fine-tune the API for our users' needs. - Object store file organization and format
InfluxDB 3 Enterprise supports a "diskless" architecture, keeping all
state in object storage. The specific file organization and format
are not part of a stable API. Only the HTTP and Apache
Arrow Flight APIs are considered stable.
Window functions let you calculate running totals, moving averages, or other aggregate-like results without collapsing rows into groups.
They perform their calculations over a “window” of rows, which you can partition and order in various ways, and return a calculated value for each row in the set.
Unlike non-window aggregate functions that combine each group into a single row, window functions preserve each row’s identity and calculate an additional value for every row in the partition.
For example, the following query uses the Home sensor sample data
and returns each temperature reading with the average temperature per room over
the queried time range:
SELECT
time,
room,
temp,
avg(temp) OVER (PARTITION BY room) AS avg_room_temp
FROM
home
WHERE
time >= '2025-03-29T08:00:00Z'
AND time <= '2025-03-29T09:00:00Z'
ORDER BY
room,
time
time | room | temp | avg_room_temp |
---|
2025-03-29T08:00:00 | Kitchen | 21.0 | 22.0 |
2025-03-29T09:00:00 | Kitchen | 23.0 | 22.0 |
2025-03-29T08:00:00 | Living Room | 21.1 | 21.25 |
2025-03-29T09:00:00 | Living Room | 21.4 | 21.25 |
As window functions operate on a row, there is a set of rows in the row’s
partition that the window function uses to perform the operation. This set of
rows is called the window frame.
Window frame boundaries can be defined using
RANGE
, ROW
, or GROUPS
frame units, each relative to the current row–for
example:
SELECT
time,
temp,
avg(temp) OVER (
ORDER BY time
RANGE INTERVAL '3 hours' PRECEDING
) AS 3h_moving_avg
FROM home
WHERE room = 'Kitchen'
SELECT
time,
temp,
avg(temp) OVER (
ROWS 3 PRECEDING
) AS moving_avg
FROM home
WHERE room = 'Kitchen'
SELECT
time,
room,
temp,
avg(temp) OVER (
ORDER BY room
GROUPS 1 PRECEDING
) AS moving_avg
FROM home
For more information about how window frames work, see the frame clause.
If you don’t specify window frames, window functions use all rows in the current
partition to perform their operation.
function([expr])
OVER(
[PARTITION BY expr[, …]]
[ORDER BY expr [ ASC | DESC ][, …]]
[ frame_clause ]
)
Window functions use an OVER
clause that directly follows the window function’s
name and arguments.
The OVER
clause syntactically distinguishes a window
function from a non-window or aggregate function and defines how to group and order rows for the window operation.
The PARTITION BY
clause in the OVER
clause divides the rows into groups, or
partitions, that share the same values of the PARTITION BY
expressions.
The window function operates on all the rows in the same partition as the
current row.
The ORDER BY
clause inside of the OVER
clause controls the order that the
window function processes rows in each partition.
When a window clause contains an ORDER BY
clause, the window frame boundaries
may be explicit or implicit, limiting a window frame size in both directions
relative to the current row.
The ORDER BY
clause in an OVER
clause determines the processing order for
rows in each partition and is separate from the ORDER BY
clause of the query.
The frame clause defines window frame boundaries and can be one of the following:
{ RANGE | ROWS | GROUPS } frame_start
{ RANGE | ROWS | GROUPS } BETWEEN frame_start AND frame_end
When defining window frames, you can use one of the following frame units:
Defines frame boundaries using rows with values for columns specified
in the ORDER BY
clause within a value range relative to
the current row value.
When using RANGE
frame units, you must include an ORDER BY
clause with
exactly one column.
The offset is the difference between the current row value and surrounding
row values. RANGE
supports the following offset types:
- Numeric (non-negative)
- Numeric string (non-negative)
- Interval
See how RANGE
frame units work with numeric offsets
To use a numeric offset with the RANGE
frame unit, you must sort partitions
by a numeric-type column.
... OVER (
ORDER BY wind_direction
RANGE BETWEEN 45 PRECEDING AND 45 FOLLOWING
)
The window frame includes rows with sort column values between 45 below and
45 above the current row’s value:
time | city | wind_direction |
---|
2025-02-17T13:00:00 | Rome | 33 |
2025-02-17T08:00:00 | Rome | 34 |
2025-02-17T23:00:00 | Rome | 49 |
2025-02-17T17:00:00 | Rome | 86 |
2025-02-17T11:00:00 | Rome | 93 |
2025-02-17T12:00:00 | Rome | 115 |
2025-02-17T10:00:00 | Rome | 156 |
See how RANGE
frame units work with interval offsets
To use an interval offset with the RANGE
frame unit, you must sort partitions
by time
or a timestamp-type column.
... OVER (
ORDER BY time
RANGE BETWEEN
INTERVAL '3 hours' PRECEDING
AND INTERVAL '1 hour' FOLLOWING
)
The window frame includes rows with timestamps between three hours before and
one hour after the current row’s timestamp:
time | room | temp |
---|
2025-03-29T08:00:00 | Kitchen | 21.0 |
2025-03-29T09:00:00 | Kitchen | 23.0 |
2025-03-29T10:00:00 | Kitchen | 22.7 |
2025-03-29T11:00:00 | Kitchen | 22.4 |
2025-03-29T12:00:00 | Kitchen | 22.5 |
2025-03-29T13:00:00 | Kitchen | 22.8 |
2025-03-29T14:00:00 | Kitchen | 22.8 |
2025-03-29T15:00:00 | Kitchen | 22.7 |
Defines window frame boundaries using row positions relative to the current row.
The offset is the difference in row position from the current row.
ROWS
supports the following offset types:
- Numeric (non-negative)
- Numeric string (non-negative)
See how ROWS
frame units work
When using the ROWS
frame unit, row positions relative to the current row
determine frame boundaries–for example:
... OVER (
ROWS BETWEEN 2 PRECEDING AND 1 FOLLOWING
)
The window frame includes the two rows before and the one row after the current row:
time | city | wind_direction |
---|
2025-02-17T08:00:00 | Rome | 34 |
2025-02-17T10:00:00 | Rome | 156 |
2025-02-17T11:00:00 | Rome | 93 |
2025-02-17T12:00:00 | Rome | 115 |
2025-02-17T13:00:00 | Rome | 33 |
2025-02-17T17:00:00 | Rome | 86 |
2025-02-17T23:00:00 | Rome | 49 |
Defines window frame boundaries using row groups.
Rows with the same values for the columns in the ORDER BY
clause
comprise a row group.
When using GROUPS
frame units, include an ORDER BY
clause.
The offset is the difference in row group position relative to the current row group.
GROUPS
supports the following offset types:
- Numeric (non-negative)
- Numeric string (non-negative)
See how GROUPS
frame units work
When using the GROUPS
frame unit, unique combinations column values specified
in the ORDER BY
clause determine each row group. For example, if you sort
partitions by country
and city
:
... OVER (
ORDER BY country, city
GROUPS ...
)
The query defines row groups in the following way:
time | country | city | wind_direction |
---|
2025-02-17T00:00:00 | France | Strasbourg | 181 |
2025-02-17T01:00:00 | France | Strasbourg | 228 |
2025-02-17T02:00:00 | France | Strasbourg | 289 |
2025-02-17T00:00:00 | France | Toulouse | 24 |
2025-02-17T01:00:00 | France | Toulouse | 210 |
2025-02-17T02:00:00 | France | Toulouse | 206 |
2025-02-17T00:00:00 | Italy | Bari | 2 |
2025-02-17T01:00:00 | Italy | Bari | 57 |
2025-02-17T00:00:00 | Italy | Bologna | 351 |
2025-02-17T01:00:00 | Italy | Bologna | 232 |
2025-02-17T02:00:00 | Italy | Bologna | 29 |
You can then use group offsets to determine frame boundaries:
... OVER (
ORDER BY country, city
GROUPS 2 PRECEDING
)
The window function uses all rows in the current row group and the two preceding row groups to perform the operation:
time | country | city | wind_direction |
---|
2025-02-17T00:00:00 | France | Strasbourg | 181 |
2025-02-17T01:00:00 | France | Strasbourg | 228 |
2025-02-17T02:00:00 | France | Strasbourg | 289 |
2025-02-17T00:00:00 | France | Toulouse | 24 |
2025-02-17T01:00:00 | France | Toulouse | 210 |
2025-02-17T02:00:00 | France | Toulouse | 206 |
2025-02-17T00:00:00 | Italy | Bari | 2 |
2025-02-17T01:00:00 | Italy | Bari | 57 |
2025-02-17T00:00:00 | Italy | Bologna | 351 |
2025-02-17T01:00:00 | Italy | Bologna | 232 |
2025-02-17T02:00:00 | Italy | Bologna | 29 |
Frame boundaries (frame_start and frame_end) define the boundaries of
each frame that the window function operates on.
Starts at the first row of the partition and ends at the current row.
Starts at offset
frame units before the current row and ends at the current row.
For example, 3 PRECEDING
includes 3 rows before the current row.
Both starts and ends at the current row when used as a boundary.
Starts at the current row and ends at offset
frame units after the current row.
For example, 3 FOLLOWING
includes 3 rows after the current row.
Starts at the current row and ends at the last row of the partition.
Use a specified offset of frame units after the current row
as a frame boundary.
Use the current row to the end of the current partition the frame boundary.
Use the WINDOW
clause to define a reusable alias for a window specification.
This is useful when multiple window functions in your query share the same window definition.
Instead of repeating the same OVER clause for each function,
define the window once and reference it by alias–for example:
SELECT
sum(net_gain) OVER w,
avg(net_net) OVER w
FROM
finance
WINDOW w AS ( PARTITION BY ticker ORDER BY time DESC);
All aggregate functions
can be used as window functions.
Returns the cumulative distribution of a value within a group of values.
The returned value is greater than 0 and less than or equal to 1 and represents
the relative rank of the value in the set of values.
The ORDER BY
clause in the OVER
clause is used
to correctly calculate the cumulative distribution of the current row value.
View cume_dist
query example
The following example uses the Home sensor sample data.
SELECT
time,
room,
temp,
cume_dist() OVER (
PARTITION BY room
ORDER BY temp
) AS cume_dist
FROM home
WHERE
time >= '2025-03-29T08:00:00Z'
AND time < '2025-03-29T12:00:00Z'
time | room | temp | cume_dist |
---|
2025-03-29T08:00:00 | Living Room | 21.1 | 0.25 |
2025-03-29T09:00:00 | Living Room | 21.4 | 0.5 |
2025-03-29T10:00:00 | Living Room | 21.8 | 0.75 |
2025-03-29T11:00:00 | Living Room | 22.2 | 1.0 |
2025-03-29T08:00:00 | Kitchen | 21.0 | 0.25 |
2025-03-29T11:00:00 | Kitchen | 22.4 | 0.5 |
2025-03-29T10:00:00 | Kitchen | 22.7 | 0.75 |
2025-03-29T09:00:00 | Kitchen | 23.0 | 1.0 |
Returns the rank of the current row in its partition.
Ranking is consecutive; assigns duplicate values the same rank number and the rank sequence continues
with the next distinct value (unlike rank()
).
The ORDER BY
clause in the OVER
clause determines
ranking order.
View dense_rank
query example
The following example uses the Home sensor sample data.
SELECT
time,
room,
temp,
dense_rank() OVER (
PARTITION BY room
ORDER BY temp
) AS dense_rank
FROM home
WHERE
time >= '2025-03-29T08:00:00Z'
AND time < '2025-03-29T12:00:00Z'
time | room | temp | dense_rank |
---|
2025-03-29T08:00:00 | Kitchen | 21.0 | 1 |
2025-03-29T11:00:00 | Kitchen | 22.4 | 2 |
2025-03-29T10:00:00 | Kitchen | 22.7 | 3 |
2025-03-29T09:00:00 | Kitchen | 23.0 | 4 |
2025-03-29T08:00:00 | Living Room | 21.1 | 1 |
2025-03-29T09:00:00 | Living Room | 21.4 | 2 |
2025-03-29T10:00:00 | Living Room | 21.8 | 3 |
2025-03-29T11:00:00 | Living Room | 22.2 | 4 |
Compare dense_rank
, rank
, and row_number
functions
Consider a table with duplicate ID values.
The following query shows how each ranking function handles duplicate values:
SELECT
id,
rank() OVER(ORDER BY id),
dense_rank() OVER(ORDER BY id),
row_number() OVER(ORDER BY id)
FROM my_table;
ID | rank | dense_rank | row_number |
---|
1 | 1 | 1 | 1 |
1 | 1 | 1 | 2 |
1 | 1 | 1 | 3 |
2 | 4 | 2 | 4 |
Key differences:
rank()
assigns the same rank to equal values but skips ranks for subsequent valuesdense_rank()
assigns the same rank to equal values and uses consecutive ranksrow_number()
assigns unique sequential numbers regardless of value (non-deterministic)
Distributes the rows in an ordered partition into the specified number of groups.
Each group is numbered, starting at one.
For each row, ntile
returns the group number to which the row belongs.
Group numbers range from 1 to the expression
value, dividing the partition as
equally as possible.
The ORDER BY
clause in the OVER
clause determines
ranking order.
- expression: An integer. The number of groups to split the partition into.
View ntile
query example
The following example uses the Home sensor sample data.
SELECT
time,
temp,
ntile(4) OVER (
ORDER BY time
) AS ntile
FROM home
WHERE
room = 'Kitchen'
AND time >= '2025-03-29T08:00:00Z'
AND time < '2025-03-29T15:00:00Z'
time | temp | ntile |
---|
2025-03-29T08:00:00 | 21.0 | 1 |
2025-03-29T09:00:00 | 23.0 | 1 |
2025-03-29T10:00:00 | 22.7 | 2 |
2025-03-29T11:00:00 | 22.4 | 2 |
2025-03-29T12:00:00 | 22.5 | 3 |
2025-03-29T13:00:00 | 22.8 | 3 |
2025-03-29T14:00:00 | 22.8 | 4 |
Returns the percentage rank of the current row within its partition.
The returned value is between 0
and 1
, computed as:
(rank - 1) / (total_rows - 1)
The ORDER BY
clause in the OVER
clause determines
the ranking order.
View percent_rank
query example
The following example uses the Home sensor sample data.
SELECT
time,
room,
temp,
percent_rank() OVER (
PARTITION BY room
ORDER BY temp
) AS percent_rank
FROM home
WHERE
time >= '2025-03-29T08:00:00Z'
AND time < '2025-03-29T11:00:00Z'
time | room | temp | percent_rank |
---|
2025-03-29T08:00:00 | Kitchen | 21.0 | 0.0 |
2025-03-29T10:00:00 | Kitchen | 22.7 | 0.5 |
2025-03-29T09:00:00 | Kitchen | 23.0 | 1.0 |
2025-03-29T08:00:00 | Living Room | 21.1 | 0.0 |
2025-03-29T09:00:00 | Living Room | 21.4 | 0.5 |
2025-03-29T10:00:00 | Living Room | 21.8 | 1.0 |
Returns the rank of the current row in its partition.
For duplicate values, rank
assigns them the same rank number, skips subsequent ranks (unlike dense_rank()
),
and then continues ranking with the next distinct value.
The ORDER BY
clause in the OVER
clause determines
ranking order.
View rank
query example
The following example uses the Home sensor sample data.
SELECT
time,
room,
temp,
rank() OVER (
PARTITION BY room
ORDER BY temp
) AS rank
FROM home
WHERE
time >= '2025-03-29T08:00:00Z'
AND time < '2025-03-29T11:00:00Z'
time | room | temp | rank |
---|
2025-03-29T08:00:00 | Living Room | 21.1 | 1 |
2025-03-29T09:00:00 | Living Room | 21.4 | 2 |
2025-03-29T10:00:00 | Living Room | 21.8 | 3 |
2025-03-29T08:00:00 | Kitchen | 21.0 | 1 |
2025-03-29T10:00:00 | Kitchen | 22.7 | 2 |
2025-03-29T09:00:00 | Kitchen | 23.0 | 3 |
Compare dense_rank
, rank
, and row_number
functions
Consider a table with duplicate ID values.
The following query shows how each ranking function handles duplicate values:
SELECT
id,
rank() OVER(ORDER BY id),
dense_rank() OVER(ORDER BY id),
row_number() OVER(ORDER BY id)
FROM my_table;
ID | rank | dense_rank | row_number |
---|
1 | 1 | 1 | 1 |
1 | 1 | 1 | 2 |
1 | 1 | 1 | 3 |
2 | 4 | 2 | 4 |
Key differences:
rank()
assigns the same rank to equal values but skips ranks for subsequent valuesdense_rank()
assigns the same rank to equal values and uses consecutive ranksrow_number()
assigns unique sequential numbers regardless of value (non-deterministic)
Returns the position of the current row in its partition, counting from 1.
The ORDER BY
clause in the OVER
clause determines
row order.
View row_number
query example
The following example uses the Home sensor sample data.
SELECT
time,
room,
temp,
row_number() OVER (
PARTITION BY room
ORDER BY temp
) AS row_number
FROM home
WHERE
time >= '2025-03-29T08:00:00Z'
AND time < '2025-03-29T11:00:00Z'
time | room | temp | row_number |
---|
2025-03-29T08:00:00 | Living Room | 21.1 | 1 |
2025-03-29T09:00:00 | Living Room | 21.4 | 2 |
2025-03-29T10:00:00 | Living Room | 21.8 | 3 |
2025-03-29T08:00:00 | Kitchen | 21.0 | 1 |
2025-03-29T10:00:00 | Kitchen | 22.7 | 2 |
2025-03-29T09:00:00 | Kitchen | 23.0 | 3 |
Compare dense_rank
, rank
, and row_number
functions
Consider a table with duplicate ID values.
The following query shows how each ranking function handles duplicate values:
SELECT
id,
rank() OVER(ORDER BY id),
dense_rank() OVER(ORDER BY id),
row_number() OVER(ORDER BY id)
FROM my_table;
ID | rank | dense_rank | row_number |
---|
1 | 1 | 1 | 1 |
1 | 1 | 1 | 2 |
1 | 1 | 1 | 3 |
2 | 4 | 2 | 4 |
Key differences:
rank()
assigns the same rank to equal values but skips ranks for subsequent valuesdense_rank()
assigns the same rank to equal values and uses consecutive ranksrow_number()
assigns unique sequential numbers regardless of value (non-deterministic)
Returns the value from the first row of the window frame.
- expression: Expression to operate on. Can be a constant, column, or
function, and any combination of arithmetic operators.
last_value
View first_value
query example
The following example uses the Home sensor sample data.
SELECT
time,
room,
temp,
first_value(temp) OVER (
PARTITION BY room
ORDER BY time
) AS first_value
FROM home
WHERE
time >= '2025-03-29T08:00:00Z'
AND time < '2025-03-29T11:00:00Z'
ORDER BY room, time
time | room | temp | first_value |
---|
2025-03-29T08:00:00 | Kitchen | 21.0 | 21.0 |
2025-03-29T09:00:00 | Kitchen | 23.0 | 21.0 |
2025-03-29T10:00:00 | Kitchen | 22.7 | 21.0 |
2025-03-29T08:00:00 | Living Room | 21.1 | 21.1 |
2025-03-29T09:00:00 | Living Room | 21.4 | 21.1 |
2025-03-29T10:00:00 | Living Room | 21.8 | 21.1 |
Returns the value from the row that is at the specified offset before the
current row in the partition. If the offset row is outside the partition,
the function returns the specified default.
lag(expression, offset, default)
- expression: Expression to operate on.
Can be a constant, column, or function, and any combination of arithmetic or
string operators.
- offset: How many rows before the current row to retrieve the value of
expression from. Default is
1
. - default: The default value to return if the offset is in the partition.
Must be of the same type as expression.
lead
View lag
query example
The following example uses the Home sensor sample data.
SELECT
time,
room,
temp,
lag(temp, 1, 0) OVER (
PARTITION BY room
ORDER BY time
) AS previous_value
FROM home
WHERE
time >= '2025-03-29T08:00:00Z'
AND time < '2025-03-29T11:00:00Z'
ORDER BY room, time
time | room | temp | previous_value |
---|
2025-03-29T08:00:00 | Kitchen | 21.0 | 0.0 |
2025-03-29T09:00:00 | Kitchen | 23.0 | 21.0 |
2025-03-29T10:00:00 | Kitchen | 22.7 | 23.0 |
2025-03-29T08:00:00 | Living Room | 21.1 | 0.0 |
2025-03-29T09:00:00 | Living Room | 21.4 | 21.1 |
2025-03-29T10:00:00 | Living Room | 21.8 | 21.4 |
Returns the value from the last row of the window frame.
- expression: Expression to operate on. Can be a constant, column, or
function, and any combination of arithmetic operators.
first_value
View last_value
query example
The following example uses the Home sensor sample data.
SELECT
time,
room,
temp,
last_value(temp) OVER (
PARTITION BY room
ORDER BY time
ROWS BETWEEN CURRENT ROW AND UNBOUNDED FOLLOWING
) AS last_value
FROM home
WHERE
time >= '2025-03-29T08:00:00Z'
AND time < '2025-03-29T11:00:00Z'
ORDER BY room, time
time | room | temp | last_value |
---|
2025-03-29T08:00:00 | Kitchen | 21.0 | 22.7 |
2025-03-29T09:00:00 | Kitchen | 23.0 | 22.7 |
2025-03-29T10:00:00 | Kitchen | 22.7 | 22.7 |
2025-03-29T08:00:00 | Living Room | 21.1 | 21.8 |
2025-03-29T09:00:00 | Living Room | 21.4 | 21.8 |
2025-03-29T10:00:00 | Living Room | 21.8 | 21.8 |
Returns the value from the row that is at the specified offset after the
current row in the partition. If the offset row is outside the partition,
the function returns the specified default.
lead(expression, offset, default)
- expression: Expression to operate on.
Can be a constant, column, or function, and any combination of arithmetic or
string operators.
- offset: How many rows before the current row to retrieve the value of
expression from. Default is
1
. - default: The default value to return if the offset is in the partition.
Must be of the same type as expression.
lag
View lead
query example
The following example uses the Home sensor sample data.
SELECT
time,
room,
temp,
lead(temp, 1, 0) OVER (
PARTITION BY room
ORDER BY time
) AS next_value
FROM home
WHERE
time >= '2025-03-29T08:00:00Z'
AND time < '2025-03-29T11:00:00Z'
ORDER BY room, time
time | room | temp | next_value |
---|
2025-03-29T08:00:00 | Kitchen | 21.0 | 23.0 |
2025-03-29T09:00:00 | Kitchen | 23.0 | 22.7 |
2025-03-29T10:00:00 | Kitchen | 22.7 | 0.0 |
2025-03-29T08:00:00 | Living Room | 21.1 | 21.4 |
2025-03-29T09:00:00 | Living Room | 21.4 | 21.8 |
2025-03-29T10:00:00 | Living Room | 21.8 | 0.0 |
Returns the value from the row that is the nth row of the window frame
(counting from 1). If the nth row doesn’t exist, the function returns null.
- expression: The expression to operator on.
Can be a constant, column, or function, and any combination of arithmetic or
string operators.
- n: Specifies the row number in the current frame and partition to reference.
View lead
query example
The following example uses the Home sensor sample data.
SELECT
time,
room,
temp,
nth_value(temp, 2) OVER (
PARTITION BY room
) AS "2nd_temp"
FROM home
WHERE
time >= '2025-02-10T08:00:00Z'
AND time < '2025-02-10T11:00:00Z'
time | room | temp | 2nd_temp |
---|
2025-02-10T08:00:00 | Kitchen | 21.0 | 22.7 |
2025-02-10T10:00:00 | Kitchen | 22.7 | 22.7 |
2025-02-10T09:00:00 | Kitchen | 23.0 | 22.7 |
2025-02-10T08:00:00 | Living Room | 21.1 | 21.8 |
2025-02-10T10:00:00 | Living Room | 21.8 | 21.8 |
2025-02-10T09:00:00 | Living Room | 21.4 | 21.8 |
Was this page helpful?
Thank you for your feedback!
Thank you for being part of our community!
We welcome and encourage your feedback and bug reports for InfluxDB 3 Enterprise and this documentation.
To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support.