Application Real-Time Monitoring Service:Use Terraform to manage remote write configurations of a Prometheus instance

Create a remote write configuration

1. Create a working directory and a file named main.tf with the following content:

   provider "alicloud" {
   }

2. Initialize the Terraform runtime environment:

   terraform init

   Expected output:

   Initializing the backend...
   
   Initializing provider plugins...
   - Checking for available provider plugins...
   - Downloading plugin for provider "alicloud" (hashicorp/alicloud) 1.90.1...
   ...
   
   You may now begin working with Terraform. Try running "terraform plan" to see
   any changes that are required for your infrastructure. All Terraform commands
   should now work.
   
   If you ever set or change modules or backend configuration for Terraform,
   rerun this command to reinitialize your working directory. If you forget, other
   commands will detect it and remind you to do so if necessary.

3. Add the remote write resource to main.tf:

   # Remote write configuration for the Prometheus instance
   resource "alicloud_arms_remote_write" "myRemoteWrite1" {
       cluster_id       = "c77e1106f429e4b46b0ee1720c*****"   # The ID of the Prometheus instance
     remote_write_yaml = <<-EOT
               remote_write:
               - name: ArmsRemoteWrite1
                 url: http://47.96.XX.XX:8080/prometheus/xxx/yyy/cn-hangzhou/api/v3/write
                 basic_auth: {username: 666, password: '******'}
                 write_relabel_configs:
                 - source_labels: [instance_id]
                   separator: ;
                   regex: si-6e2ca86444db4e5*****
                   replacement: $1
                   action: keep
           EOT

   The following table describes the parameters:

   Parameter	Description
   cluster_id	The ID of the Prometheus instance.
   remote_write_yaml	The YAML block that defines the remote write configuration.
   name	The name of the remote write configuration.
   url	The remote write endpoint URL.
   basic_auth	The authentication credentials (username and password).
   write_relabel_configs	Relabeling rules that filter metrics before sending. Includes source_labels, separator, regex, replacement, and action.

4. Preview the changes:

   terraform plan

   Expected output:

   Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
     + create
   
   Terraform will perform the following actions:
   
     # alicloud_arms_remote_write.ack-rw1 will be created
     + resource "alicloud_arms_remote_write" "ack-rw1" {
         + cluster_id        = "c77e1106f429e4b46b0ee1720c*****"
         + id                = (known after apply)
         + remote_write_name = (known after apply)
         + remote_write_yaml = <<-EOT
               remote_write:
               - name: ArmsRemoteWrite1
                 url: http://xx.xx.xx.xx:8080/prometheus/xxx/yyy/cn-hangzhou/api/v3/write
                 basic_auth: {username: 666, password: '******'}
                 write_relabel_configs:
                 - source_labels: [instance_id]
                   separator: ;
                   regex: si-6e2ca86444db4e5*****
                   replacement: $1
                   action: keep
           EOT
       }
   
   Plan: 1 to add, 0 to change, 0 to destroy.

5. Apply the configuration:

   terraform apply

   Expected output:

   Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
     + create
   
   Terraform will perform the following actions:
   
     # alicloud_arms_remote_write.ack-rw1 will be created
     + resource "alicloud_arms_remote_write" "ack-rw1" {
         + cluster_id        = "c77e1106f429e4b46b0ee1720c9*****"
         + id                = (known after apply)
         + remote_write_name = (known after apply)
         + remote_write_yaml = <<-EOT
               remote_write:
               - name: ArmsRemoteWrite1
                 url: http://xx.xx.xx.xx:8080/prometheus/xxx/yyy/cn-hangzhou/api/v3/write
                 basic_auth: {username: 666, password: '******'}
                 write_relabel_configs:
                 - source_labels: [instance_id]
                   separator: ;
                   regex: si-6e2ca86444db4e5*****
                   replacement: $1
                   action: keep
           EOT
       }
   
   Plan: 1 to add, 0 to change, 0 to destroy.
   
   Do you want to perform these actions?
     Terraform will perform the actions described above.
     Only 'yes' will be accepted to approve.
   
     Enter a value: yes

   If yes is returned, the remote write configuration is created for the Prometheus instance.

Verify the creation in the console

1. Log on to the ARMS console.

2. In the left navigation pane, choose Managed Service for Prometheus > Instances.

3. Click the name of the Managed Service for Prometheus instance instance that you want to manage to go to the Integration Center page.

4. Click custom in the Installed section. In the panel that appears, click the Remote Write tab to view the created remote write configuration.

Delete the remote write configuration

Run the following command to delete the remote write configuration that was created by Terraform:

terraform destroy

Expected output:

...
Do you really want to destroy all resources?
  Terraform will destroy all your managed infrastructure, as shown above.
  There is no undo. Only 'yes' will be accepted to confirm.

  Enter a value: yes
...
Destroy complete! Resources: 1 destroyed.

Verify the deletion in the console

1. Log on to the ARMS console.

2. In the left navigation pane, choose Managed Service for Prometheus > Instances.

3. Click the name of the Managed Service for Prometheus instance instance that you want to manage to go to the Integration Center page.

4. Click custom in the Installed section. In the panel that appears, click the Remote Write tab. If the remote write configuration no longer appears, it has been deleted.