InfluxDB Cloud system buckets
InfluxDB system buckets contain time series data used by and generated from the InfluxDB monitoring and alerting system and the task engine.
Each InfluxDB organization includes the following system buckets:
The system bucket schemas below reference InfluxDB data elements. For more information, see InfluxDB key concepts.
_monitoring system bucket
The _monitoring
system bucket stores InfluxDB data used to
monitor data and send alerts.
Data retention: 7 days
_monitoring bucket schema
-
statuses (measurement)
- tags:
- _check_id: check ID
- _check_name: check name
- _level: level evaluated by the check (ok, info, warn, or crit)
- _source_measurement: original measurement queried by the check
- _type: check type (threshold or deadman)
- other tags inherited from queried data or added in the check configuration
- fields:
- _message: message generated by the check
- _source_timestamp: original timestamp of the queried data
- other fields inherited from queried data
- tags:
-
notifications (measurement)
- tags:
- _check_id: check ID that triggered the notification
- _check_name: check name that triggered the notification
- _level: check-evaluated level that triggered the notification (ok, info, warn, or crit)
- _notification_endpoint_id: notification endpoint ID
- _notification_endpoint_name: notification endpoint name
- _notification_rule_id: notification rule ID
- _notification_rule_name: notification rule name
- _sent: sent status (true or false)
- _source_measurement: original measurement queried by the check
- _type: check type (threshold or deadman)
- other tags inherited from queried data or added in the check configuration
- fields:
- _message: message generated by the check
- _source_timestamp: original timestamp of the queried data
- _status_timestamp: timestamp when the status (
_level
) was evaluated - other fields inherited from queried data
- tags:
-
rejected_points (measurement)
- tags:
- bucket: ID of the bucket targeted in the write request
- reason: brief description of why InfluxDB rejected the point
- field: field name of the point (present if the point contained a field)
- measurement: measurement of the point (present if the point contained a measurement)
- gotType: InfluxDB field type in the point (present if type mismatch)
- wantType: InfluxDB field type in the bucket schema (present if type mismatch)
- fields:
- _field:
count
(for data type and schema conflicts) orerror
(for parsing errors) - _value:
1
if_field: "count"
or error details if_field: "error"
- timestamp: time the rejected point was logged
- _field:
- tags:
_tasks system bucket
The _tasks
system bucket stores data related to InfluxDB task executions.
Data retention: 3 days
_tasks bucket schema
A task run refers to a single task execution.
- runs (measurement)
- tags:
- status: task run status (success or failed)
- taskID: task ID
- fields:
- finishedAt: timestamp when the task run finished
- logs: log output from the task run
- requestedAt: timestamp when the task run was requested
- runID task run ID
- scheduledFor: timestamp the task run was scheduled for
- startedAt: timestamp when the task run started
- tags:
Was this page helpful?
Thank you for your feedback!
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB and this documentation. To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support.