mirror of
https://github.com/VictoriaMetrics/VictoriaMetrics.git
synced 2024-11-21 14:44:00 +00:00
docs: add API doc for cloud (#7164)
### Describe Your Changes Please provide a brief description of the changes you made. Be as specific as possible to help others understand the purpose and impact of your modifications. ### Checklist The following checks are **mandatory**: - [x] My change adheres [VictoriaMetrics contributing guidelines](https://docs.victoriametrics.com/contributing/). Signed-off-by: Artem Navoiev <tenmozes@gmail.com>
This commit is contained in:
parent
dde2a0cb25
commit
504da7d02b
2 changed files with 50 additions and 0 deletions
BIN
docs/victoriametrics-cloud/api-1.webp
Normal file
BIN
docs/victoriametrics-cloud/api-1.webp
Normal file
Binary file not shown.
After Width: | Height: | Size: 16 KiB |
50
docs/victoriametrics-cloud/api.md
Normal file
50
docs/victoriametrics-cloud/api.md
Normal file
|
@ -0,0 +1,50 @@
|
|||
---
|
||||
weight: 8
|
||||
title: VictoriaMetrics Cloud API Documentation
|
||||
menu:
|
||||
docs:
|
||||
parent: "cloud"
|
||||
weight: 8
|
||||
name: API
|
||||
---
|
||||
VictoriaMetrics Cloud provides programmatic access for managing cloud resources and is useful for automation with tools like Terraform, OpenTofu, Infrastructure as a Code, GitOps framework, etc.
|
||||
|
||||
## Key Concepts
|
||||
|
||||
* **API Keys**: Used to manage VictoriaMetrics Cloud resources via API.
|
||||
|
||||
**Note: Access Tokens** are used for reading and writing data to deployments. They are separate from API Keys and should not be confused. API Keys are specifically for managing resources via the API, while Access Tokens handle data access for deployments.
|
||||
|
||||
## API Swagger/OpenAPI Reference: [https://cloud.victoriametrics.com/api-docs](https://cloud.victoriametrics.com/api-docs)
|
||||
|
||||
## API Key Properties:
|
||||
|
||||
* **Name**: Human-readable, for team context.
|
||||
* **Lifetime**: Key expiration date (no expiration is an option).
|
||||
* **Permissions**: Read-only or Read/Write access.
|
||||
* **Deployment Access**: Limit access to single, multiple, or all deployments. ***Note**: selecting all deployments in the list and the “All” option are not the same thing, the “All" option will also apply to future deployments that are created.*
|
||||
* **Key ID**: Programmatically generated identifier. It's sensitive data used for Authentication. Any operation with API keys (including viewing Key ID), will be recorded in the Audit Log.
|
||||
|
||||
![Create API Key](api-1.webp)
|
||||
|
||||
## Authentication:
|
||||
|
||||
* **API Key Creation**: Required for using the VictoriaMetrics Cloud API. You need to issue the key manually [here](https://cloud.victoriametrics.com/api_keys) or check this [Guide here](https://docs.victoriametrics.com).
|
||||
* **HTTP Header**:
|
||||
* **Header Name**: `X-VM-Cloud-Access`
|
||||
* **Header Value**: `<Key-Id>`
|
||||
|
||||
## Alerting & Recording Rules API:
|
||||
|
||||
* **List Files**: [API reference](https://cloud.victoriametrics.com/api-docs)
|
||||
* **View File**: [API reference](https://cloud.victoriametrics.com/api-docs)
|
||||
* **Upload File**: [API reference](https://cloud.victoriametrics.com/api-docs)
|
||||
* **Delete File**: [API reference](https://cloud.victoriametrics.com/api-docs)
|
||||
|
||||
For detailed setup instructions, check the [VictoriaMetrics Cloud - AlertManager Setup Guide](https://docs.victoriametrics.com/victoriametrics-cloud/alertmanager-setup-for-deployment/).
|
||||
|
||||
## Future API Features:
|
||||
|
||||
* **Deployments**: Create, Delete, Update, List, Get.
|
||||
* **Access Token**: Create, Delete, List, Get/Reveal.
|
||||
* **AlertManager**: Get Config, Upsert Config.
|
Loading…
Reference in a new issue