docs/victoriametrics-cloud: update images in the cloud documentation (#7210)

### Describe Your Changes

Update images with updated interface of the cloud solution

### Checklist

The following checks are **mandatory**:

- [ x] My change adheres [VictoriaMetrics contributing
guidelines](https://docs.victoriametrics.com/contributing/).

(cherry picked from commit c910c1c6b8)
This commit is contained in:
Dmytro Kozlov 2024-10-10 09:08:32 +02:00 committed by hagen1778
parent 2c0892263f
commit c010325acf
No known key found for this signature in database
GPG Key ID: 3BF75F3741CA9640
45 changed files with 20 additions and 16 deletions

Binary file not shown.

Before

Width:  |  Height:  |  Size: 32 KiB

After

Width:  |  Height:  |  Size: 201 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 34 KiB

After

Width:  |  Height:  |  Size: 209 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 50 KiB

After

Width:  |  Height:  |  Size: 246 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 36 KiB

After

Width:  |  Height:  |  Size: 188 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 37 KiB

After

Width:  |  Height:  |  Size: 185 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 16 KiB

View File

@ -25,7 +25,7 @@ VictoriaMetrics Cloud provides programmatic access for managing cloud resources
* **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.* * **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** or **Key Value**: Programmatically generated identifier. It's sensitive data used for Authentication. Any operation with API keys (including viewing/revealing Key Value), will be recorded in the [Audit Log](https://docs.victoriametrics.com/victoriametrics-cloud/audit-logs/). * **Key** or **Key Value**: Programmatically generated identifier. It's sensitive data used for Authentication. Any operation with API keys (including viewing/revealing Key Value), will be recorded in the [Audit Log](https://docs.victoriametrics.com/victoriametrics-cloud/audit-logs/).
![Create API Key](api-1.webp) ![Create API Key](api_keys.webp)
## Authentication: ## Authentication:

Binary file not shown.

After

Width:  |  Height:  |  Size: 171 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 15 KiB

After

Width:  |  Height:  |  Size: 176 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 18 KiB

After

Width:  |  Height:  |  Size: 184 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 52 KiB

After

Width:  |  Height:  |  Size: 207 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 34 KiB

After

Width:  |  Height:  |  Size: 207 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 80 KiB

After

Width:  |  Height:  |  Size: 199 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 67 KiB

After

Width:  |  Height:  |  Size: 180 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 107 KiB

After

Width:  |  Height:  |  Size: 229 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 44 KiB

After

Width:  |  Height:  |  Size: 208 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 161 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 76 KiB

After

Width:  |  Height:  |  Size: 190 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 175 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 171 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 73 KiB

After

Width:  |  Height:  |  Size: 218 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 13 KiB

After

Width:  |  Height:  |  Size: 106 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 5.8 KiB

After

Width:  |  Height:  |  Size: 200 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 37 KiB

After

Width:  |  Height:  |  Size: 206 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 27 KiB

After

Width:  |  Height:  |  Size: 106 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 17 KiB

After

Width:  |  Height:  |  Size: 199 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 24 KiB

After

Width:  |  Height:  |  Size: 199 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 45 KiB

After

Width:  |  Height:  |  Size: 175 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 67 KiB

After

Width:  |  Height:  |  Size: 221 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 60 KiB

After

Width:  |  Height:  |  Size: 241 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 235 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 41 KiB

After

Width:  |  Height:  |  Size: 119 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 32 KiB

After

Width:  |  Height:  |  Size: 112 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 38 KiB

After

Width:  |  Height:  |  Size: 117 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 102 KiB

After

Width:  |  Height:  |  Size: 268 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 111 KiB

After

Width:  |  Height:  |  Size: 134 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 98 KiB

After

Width:  |  Height:  |  Size: 123 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 52 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 41 KiB

After

Width:  |  Height:  |  Size: 65 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 107 KiB

After

Width:  |  Height:  |  Size: 288 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 111 KiB

After

Width:  |  Height:  |  Size: 230 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 108 KiB

After

Width:  |  Height:  |  Size: 223 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 97 KiB

After

Width:  |  Height:  |  Size: 124 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 103 KiB

After

Width:  |  Height:  |  Size: 282 KiB

View File

@ -57,11 +57,9 @@ You will be redirected to the main page with a notification message to confirm y
You will also receive an email with a confirmation link as shown on the picture below: You will also receive an email with a confirmation link as shown on the picture below:
![Signup email](quick_start_signup_email.webp)
![Signup email confirm](quick_start_signup_email_confirm.webp)
It is necessary to confirm your email address. Otherwise, you won't be able to create a deployment. It is necessary to confirm your email address. Otherwise, you won't be able to create a deployment.
![Signup email confirm](quick_start_signup_email_confirm.webp)
After successful confirmation of your email address, you'll be able to [create your first deployment](#creating-deployments) or [add a payment method](#adding-a-payment-method). After successful confirmation of your email address, you'll be able to [create your first deployment](#creating-deployments) or [add a payment method](#adding-a-payment-method).
@ -70,7 +68,7 @@ After successful confirmation of your email address, you'll be able to [create y
## Adding a payment method ## Adding a payment method
1. Navigate to a [Billing](https://console.victoriametrics.cloud/billing?utm_source=website&utm_campaign=docs_quickstart) page or click on `Upgrade` button as shown below: 1. Navigate to a [Billing](https://console.victoriametrics.cloud/billing?utm_source=website&utm_campaign=docs_quickstart) page:
![Add payment method](how_to_add_payment_method_upgrade.webp) ![Add payment method](how_to_add_payment_method_upgrade.webp)
@ -86,7 +84,7 @@ After successful confirmation of your email address, you'll be able to [create y
![Add payment method add card](how_to_add_payment_method_add_card.webp) ![Add payment method add card](how_to_add_payment_method_add_card.webp)
1. An error message will appear if a card us invalid 1. An error message will appear if a card is invalid
![Add payment method invalid card](how_to_add_payment_method_invalid_card.webp) ![Add payment method invalid card](how_to_add_payment_method_invalid_card.webp)
@ -157,11 +155,8 @@ If you forgot your password, it can be restored in the following way:
![Restore password email](quick_start_restore_password_email_field.webp) ![Restore password email](quick_start_restore_password_email_field.webp)
![Restore password message](quick_start_restore_password_message.webp) ![Restore password message](quick_start_restore_password_message.webp)
1. Follow the instructions sent to your email in order to get access to your VictoriaMetrics Cloud account: 1. Follow the instructions sent to your email in order to get access to your VictoriaMetrics Cloud account:
![Restore password email](quick_start_restore_password_email.webp) ![Restore password email](quick_start_restore_password_email.webp)
@ -187,7 +182,7 @@ To create a deployment click on the button `Start sending metrics` button:
![Create deployment start](create_deployment_start.webp) ![Create deployment start](create_deployment_start.webp)
When you already have at least one deployment you can create a new one by clicking on the `Create deployment` button: When you already have at least one deployment you can create a new one by clicking on the `Create` button:
![Create deployment continue](create_deployment_continue.webp) ![Create deployment continue](create_deployment_continue.webp)
@ -249,16 +244,24 @@ You'll also be notified via email once your deployment is ready to use:
After transition from `PROVISIONING` to `RUNNING` state, VictoriaMetrics Cloud deployment is fully operational After transition from `PROVISIONING` to `RUNNING` state, VictoriaMetrics Cloud deployment is fully operational
and is ready to accept write and read requests. and is ready to accept write and read requests.
Click on deployment name and navigate to the Access tab to get the access token: Click on right three dots and navigate to the Access menu to get the access token:
![Deployment access](deployment_access.webp) ![Deployment access](deployment_access.webp)
Click on the `Generate token`. Fill `Name` field. Select token `Permission` and click `Generate` button:
![Deployment generate access token](deployment_access_generate_token.webp)
Generated token will be shown in the list of access tokens. Click on the three dots and choose `Show examples` to see the usage examples:
![Deployment access token](deployment_access_token_generated.webp)
Access tokens are used in token-based authentication to allow an application to access the VictoriaMetrics API. Access tokens are used in token-based authentication to allow an application to access the VictoriaMetrics API.
Supported token types are `Read-Only`, `Write-Only` and `Read-Write`. Click on token created by default Supported token types are `Read-Only`, `Write-Only` and `Read-Write`. Click on three dots in `Actions` and select `Show examples`
to see usage examples: in the dropdown to see usage examples:
![Deployment access token examples](deployment_access_token_examples.webp)
![Deployment access write example](deployment_access_write_example.webp) ![Deployment access write example](deployment_access_write_example.webp)
@ -284,6 +287,7 @@ To discover additional configuration options click on `Advanced Settings` button
![Modify deployment additional settings](modify_deployment_additional_settings.webp) ![Modify deployment additional settings](modify_deployment_additional_settings.webp)
![Modify deployment additional settings with description](modify_deployment_additional_settings_with_description.webp)
In that section, additional params can be set: In that section, additional params can be set: