Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Tutorials
    • All tutorials
    • Setting up a Managed Service for PostgreSQL connection from a container in Serverless Containers
    • Creating a VM from a Container Optimized Image
    • Creating a VM from a Container Optimized Image with an additional volume for a Docker container
    • Creating an instance group from a Container Optimized Image with multiple Docker containers
    • Creating an instance group from a Container Optimized Image
    • Creating a VM from a Container Optimized Image with multiple Docker containers
    • Updating a Container Optimized Image VM
    • Configuring data output from a Docker container to a serial port
      • Creating a new Kubernetes project
      • Creating a Kubernetes cluster with no internet access
      • Running workloads with GPUs
      • Using node groups with GPUs and no pre-installed drivers
      • Setting up Time-Slicing GPUs
      • Migrating resources to a different availability zone
      • Encrypting secrets
        • Cluster monitoring with Prometheus and Grafana
        • Managed Service for Kubernetes cluster monitoring with Filebeat OSS

In this article:

  • Required paid resources
  • Getting started
  • Install Filebeat OSS
  • Check the result
  • Delete the resources you created
  1. Container infrastructure
  2. Managed Service for Kubernetes
  3. Monitoring
  4. Managed Service for Kubernetes cluster monitoring with Filebeat OSS

Yandex Managed Service for Kubernetes cluster monitoring with Filebeat OSS

Written by
Yandex Cloud
Updated at May 5, 2025
  • Required paid resources
  • Getting started
  • Install Filebeat OSS
  • Check the result
  • Delete the resources you created

Filebeat OSS is a plugin for collecting and forwarding logs to the OpenSearch ecosystem. Installed in a Managed Service for Kubernetes cluster, Filebeat collects cluster and pod logs, and forwards them to Yandex Managed Service for OpenSearch.

To set up Managed Service for Kubernetes cluster monitoring with Filebeat OSS:

  1. Install Filebeat OSS.
  2. Check the result.

If you no longer need the resources you created, delete them.

Required paid resourcesRequired paid resources

The support cost includes:

  • Fee for the Managed Service for Kubernetes cluster: using the master and outgoing traffic (see Managed Service for Kubernetes pricing).
  • Cluster nodes (VM) fee: using computing resources, operating system, and storage (see Compute Cloud pricing).
  • Managed Service for OpenSearch cluster fee: using computing resources allocated to hosts (including hosts with the MANAGER role) and disk space (see Managed Service for OpenSearch pricing).
  • Fee for public IP addresses for Managed Service for OpenSearch cluster hosts and Managed Service for Kubernetes cluster nodes if public access is enabled for them (see Virtual Private Cloud pricing).

Getting startedGetting started

  1. Create a Managed Service for Kubernetes cluster and a node group.

    Manually
    Terraform
    1. If you do not have a network yet, create one.

    2. If you do not have any subnets yet, create them in the availability zones where your Managed Service for Kubernetes cluster and node group will be created.

    3. Create security groups for the Managed Service for Kubernetes cluster and its node groups.

      Warning

      The configuration of security groups determines the performance and availability of the cluster and the services and applications running in it.

    4. Create a Managed Service for Kubernetes cluster and a node group in any suitable configuration. When creating them, specify the security groups prepared earlier.

    1. If you do not have Terraform yet, install it.

    2. Download the file with provider settings. Place it in a separate working directory and specify the parameter values.

    3. Download the k8s-cluster.tf configuration file of the Managed Service for Kubernetes cluster to the same working directory. This file describes:

      • Network.

      • Subnet.

      • Managed Service for Kubernetes cluster.

      • Service account required for the Managed Service for Kubernetes cluster and node group.

      • Security groups which contain rules required for the Managed Service for Kubernetes cluster and its node groups.

        Warning

        The configuration of security groups determines the performance and availability of the cluster and the services and applications running in it.

    4. Specify the following in the configuration file:

      • Folder ID.
      • Kubernetes version for the Managed Service for Kubernetes cluster and node groups.
      • Managed Service for Kubernetes cluster CIDR.
      • Service account name. The name must be unique within the folder.
    5. Run the terraform init command in the directory with the configuration files. This command initializes the provider specified in the configuration files and enables you to use the provider resources and data sources.

    6. Check that the Terraform configuration files are correct using this command:

      terraform validate
      

      If there are any errors in the configuration files, Terraform will point them out.

    7. Create the required infrastructure:

      1. Run this command to view the planned changes:

        terraform plan
        

        If you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.

      2. If everything looks correct, apply the changes:

        1. Run this command:

          terraform apply
          
        2. Confirm updating the resources.

        3. Wait for the operation to complete.

      All the required resources will be created in the specified folder. You can check resource availability and their settings in the management console.

  2. Install kubect and configure it to work with the new cluster.

  3. Create a Managed Service for OpenSearch cluster with any suitable configuration.

Install Filebeat OSSInstall Filebeat OSS

Install Filebeat OSS by following this guide.

Check the resultCheck the result

Make sure that the Managed Service for OpenSearch cluster is receiving logs from the Managed Service for Kubernetes cluster:

Bash
OpenSearch Dashboards

Run this command:

curl \
  --user admin:<Managed_Service_for_OpenSearch_cluster_admin_user_password> \
  --cacert CA.pem \
  --request GET 'https://<name_of_OpenSearch_host_with_DATA_role>:9200/_cat/indices?v'
  1. Connect to the Managed Service for OpenSearch cluster using OpenSearch Dashboards.
  2. Select the Global tenant.
  3. Open the control panel by clicking .
  4. Under OpenSearch Plugins, select Index Management.
  5. Go to Indexes.

The list should contain filebeat-7.12.1-<log_date> indexes with the Managed Service for Kubernetes cluster logs.

Delete the resources you createdDelete the resources you created

Some resources are not free of charge. Delete the resources you no longer need to avoid paying for them.

Delete the Managed Service for OpenSearch cluster.

Delete the other resources depending on how they were created:

Manually
Terraform
  1. Delete the Managed Service for Kubernetes cluster.
  2. Delete the created subnets and networks.
  3. Delete the created service account.
  1. In the terminal window, go to the directory containing the infrastructure plan.

    Warning

    Make sure the directory has no Terraform manifests with the resources you want to keep. Terraform deletes all resources that were created using the manifests in the current directory.

  2. Delete resources:

    1. Run this command:

      terraform destroy
      
    2. Confirm deleting the resources and wait for the operation to complete.

    All the resources described in the Terraform manifests will be deleted.

Was the article helpful?

Previous
Cluster monitoring with Prometheus and Grafana
Next
Integration with Argo CD
© 2025 Direct Cursus Technology L.L.C.