InfluxDB Cloud is a fully managed, scalable, and secure time series database service designed for real-time analytics and monitoring.
Tool to add a cell to a dashboard. Use when you want to add or copy a cell to an existing dashboard after verifying the dashboard exists.
Delete a user from InfluxDB Cloud by their user ID. This action permanently removes a user from the InfluxDB Cloud organization. Requires an operator token with write:users permission to execute successfully. Use this when you need to remove a user's access to the InfluxDB Cloud organization.
Generates an Abstract Syntax Tree (AST) from a Flux query script. Use this tool to analyze the structure of a Flux query and validate its syntax. The AST shows the parsed structure but does not validate semantic correctness (e.g., whether buckets or fields exist).
Retrieve a Database and Retention Policy (DBRP) mapping by ID from InfluxDB Cloud. DBRP mappings enable InfluxDB 1.x query compatibility by mapping old database/retention policy names to InfluxDB 2.x buckets. Use this action to: - Verify which bucket a 1.x database/retention policy maps to - Check if a mapping is the default for its database - Inspect mapping configuration before updating or querying data with 1.x APIs Prerequisites: You must have a valid DBRP mapping ID (obtain via listing DBRP mappings or from previous create operations).
Lists all available InfluxDB v2 API endpoints and routes. This action queries the root API endpoint (GET /api/v2) to retrieve a comprehensive map of all available API resources and their corresponding URLs. Use this to discover what endpoints are available in your InfluxDB Cloud instance, including resources for data management (buckets, write, delete, query), user management (users, orgs, authorizations), monitoring (checks, tasks, dashboards), and configuration (labels, variables, Telegraf). The response includes both simple route strings (e.g., "/api/v2/buckets") and nested route objects (e.g., query routes with analyze, ast, suggestions endpoints). Authentication: Requires a valid authorization token in the metadata headers.
Authenticates a user with username and password to create a session with InfluxDB Cloud. Returns a session cookie that can be used for subsequent API requests instead of token-based authentication. Use this when you need to authenticate with user credentials rather than API tokens, or when establishing a user session for operations that require session-based authentication.