- What's New
- Function Overview
- Service Overview
- Billing
- Getting Started
-
User Guide
- Buying SecMaster
- Authorizing SecMaster
- Viewing Security Overview
- Workspaces
- Viewing Purchased Resources
- Security Situation
- Resource Manager
- Risk Prevention
- Threat Operations
- Security Orchestration
-
Playbook Overview
- Ransomware Incident Response Solution
- Attack Link Analysis Alert Notification
- HSS Isolation and Killing of Malware
- Automatic Renaming of Alert Names
- Auto High-Risk Vulnerability Notification
- Automatic Notification of High-Risk Alerts
- Auto Blocking for High-risk Alerts
- Real-time Notification of Critical Organization and Management Operations
-
Settings
- Data Integration
-
Log Data Collection
- Data Collection Overview
- Adding a Node
- Configuring a Component
- Adding a Connection
- Creating and Editing a Parser
- Adding and Editing a Collection Channel
- Managing Connections
- Managing Parsers
- Managing Collection Channels
- Viewing Collection Nodes
- Managing Nodes and Components
- Partitioning a Disk
- Logstash Configuration Description
- Connector Rules
- Parser Rules
- Upgrading the Component Controller
- Customizing Directories
- Permissions Management
- Key Operations Recorded by CTS
-
Best Practices
-
Log Access and Transfer Operation Guide
- Solution Overview
- Resource Planning
- Process Flow
-
Procedure
- (Optional) Step 1: Buy an ECS
- (Optional) Step 2: Buy a Data Disk
- (Optional) Step 3: Attach a Data Disk
- Step 4: Create a Non-administrator IAM User
- Step 5: Configure Network Connection
- Step 6: Install the Component Controller (isap-agent)
- Step 7: Install the Log Collection Component (Logstash)
- (Optional) Step 8: Creating a Log Storage Pipeline
- Step 9: Configure a Connector
- (Optional) Step 10: Configure a Log Parser
- Step 11: Configure a Log Collection Channel
- Step 12: Verify Log Access and Transfer
- Credential Leakage Response Solution
-
Log Access and Transfer Operation Guide
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
API
- Alert Management
- Incident Management
- Indicator Management
- Playbook Management
- Alert Rule Management
- Playbook Version Management
- Playbook Rule Management
- Playbook Instance Management
- Playbook Approval Management
- Playbook Action Management
- Incident Relationship Management
- Data Class Management
- Workflow Management
- Data Space Management
- Pipelines
- Workspace Management
- Metering and Billing
- Metric Query
- Baseline Inspection
- Appendix
- FAQs
Show all
Partitioning a Disk
To keep collectors healthy for you to collect security data, there are some limitations and constraints.
- Only non-administrator IAM users can be used for installing isap-agent.
- Make sure the /opt/cloud directory where you install isap-agent and use the collector has at least 100 GB of free disk space.
When you install the isap-agent in the /opt directory on an ECS, if the message shown in Figure 1 is displayed, the space of the /opt directory is insufficient.
To ensure at least 100 GB space is available in the directory where the component controller isap-agent is installed, you may need to partition the disk.
The procedure is as follows:
- Buy and attach a disk.
- Log in to the management console.
- Click
in the upper left corner and select the region and project.
- In the upper left corner of the page, click
and choose Compute > Elastic Cloud Server. In the ECS list, click the name of the ECS where isap-agent is installed to go to the ECS details page.
- Click the Disks tab. On the displayed page, click Add Disk.
- On the displayed page, buy a disk with Disk Specifications set to 100 GiB.
For details, see Purchasing an EVS Disk.
- After the disk is successfully attached, you can view the attached disk on the Disks tab for the ECS.
After a data disk is attached to a server, you must log in to the server and initialize the disk before you can use the disk. For details about how to initialize a data disk, see Initializing an EVS Data Disk.
- Partition the disk.
- Log in to the node where isap-agent is installed and run the following command to check the disk usage:
- Run the following command to partition the disk:
sh /opt/cloud/isap-agent/action/agent_controller_linux.sh partition
If the following information is displayed, the disk is partitioned successfully.
Figure 3 Disk partitions
- Reinstall the component controller isap-agent. For details, see Managing Nodes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.