Procedure for Using Logstash
Category |
Operation |
Details |
|
---|---|---|---|
Use |
Planning a cluster |
Before creating a Logstash cluster, develop a plan for it, such as whether to deploy the cluster across multiple AZs to improve availability; and the node quantity and specifications in order to ensure the desired performance and reliability. |
|
Creating a cluster |
Create a Logstash cluster based on the plan. |
||
Configuring routes |
If the Logstash cluster and the data source are connected to the same primary NIC, the network is automatically connected. Otherwise, you need to configure routes connecting each node of the Logstash cluster to the data source and back. |
||
Configuring a Logstash migration task |
Through the configuration center of the Logstash cluster, you can create and start a Logstash configuration file to migrate data between different locations. |
||
O&M |
Scaling a cluster |
CSS provides flexible scale-out and scale-in options, using which you can add or reduce nodes, and increase or reduce node specifications. This allows you to dynamically adjust cluster resources to meet changing demand and optimize costs. |
|
Managing clusters |
CSS provides comprehensive cluster management functions. Users can view cluster information, manage tags, bind clusters with enterprise projects, and upload custom CA certificates. They help users efficiently manage Logstash clusters. |
Viewing Logstash Cluster Information Setting Tags for a Logstash Cluster Binding a Logstash Cluster to an Enterprise Project Managing CA Certificates for a Logstash Cluster |
|
Monitoring and log management |
CSS provides comprehensive monitoring and log management. Users can configure and check monitoring metrics for clusters, nodes, and Logstash pipelines, configure alarm rules, and back up and view logs. They help users efficiently monitor and analyze the performance of Logstash clusters, ensuring cluster reliability. |
Monitoring Metrics for Logstash Clusters in Cloud Eye |
|
Audit logs |
Cloud Trace Service (CTS) can be used to log mission-critical operations related to Logstash clusters. Used for auditing and accountability purposes, these records are retained for seven days on the management console. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot