Host Resource Requirements

Understand the minimum host resource requirements for SmartAgent to ensure correct deployment and operation.

---

Overview

To ensure SmartAgent runs properly and provides accurate data, your host must meet the following resource requirements. The data below is based on version 9.0.0.

---

CPU

• Minimum Requirement: 4-core CPU

---

Memory

SmartAgent itself consumes very little memory. Application agents (e.g., javaagent) run as child threads of the business process and may consume additional memory based on the complexity of the application and monitoring needs. If your application has already set memory limits, it is recommended to reassess based on the original limits.

info

The recommended values below are for general reference. Please adjust according to actual application startup speed and load testing results.

Recommended calculation formula:

Additional memory requirement = 256MB + (Original memory limit × 10%)

Java commandline limits example

# Original
java -Xmx1024m -jar app.jar

# After adjustment
java -Xmx1356m -jar app.jar

Pod limits example

# Original
resources:
  limits:
    memory: "1024Mi"
  requests:
    memory: "1024Mi"

# After adjustment
resources:
  limits:
    memory: "1356Mi"
  requests:
    memory: "1356Mi"

---

Disk Space Requirements

OS	Installation Directory	Runtime Directory
Linux	Root install: /opt/bonree/apm Non-root install: $HOME	Root install: /var/lib/bonree/apm Non-root install: $HOME/.smartagent
Windows	C:\Program Files (x86)\bonree	C:\ProgramData\bonree

info

An additional 20GB of disk space is required on the host for temporary storage of core files generated in case of process crashes.
Normally, this space is not used. To completely disable crash analysis, see: Installation Parameters -> disable-dumpproc

Directory	Linux x86_x64	Linux ARM	Windows
Installation Directory (excluding logs, cache)	~550MB	~380MB	~320MB
logs	Host root install: ~22.8GB Containerized or non-root install: ~2.8GB	Host root install: ~22.8GB Containerized or non-root install: ~2.8GB	~2.1GB
cache	~(Number of agent instances + 2) * 100MB	~(Number of agent instances + 2) * 100MB	~(Number of agent instances + 1) * 100MB
Runtime Directory	~1MB	~1MB	~1MB
Total	Host root install: ~23.4GB + (Number of agent instances + 2) * 100MB Containerized or non-root install: ~3.4GB + (Number of agent instances + 2) * 100MB	Host root install: ~23.4GB + (Number of agent instances + 2) * 100MB Containerized or non-root install: ~3.4GB + (Number of agent instances + 2) * 100MB	~2.4GB + (Number of agent instances + 2) * 100MB

---

Detailed Disk Space for logs Directory

Directory	Linux	Windows
process/java/php/containers etc.	~2GB	~2GB
machine	~120MB	~80MB
ebpfagent	~200MB	0
profiling-agent	~40MB	0
logsagent	~400MB	0
agentdumpproc (Host root install only)	~20GB (temporary core files generated on crashes; deleted after analysis)	0
npd	~40MB	0
Total	Host root install: ~22.8GB Containerized or non-root install: ~2.8GB	~2.1GB

---

cache Directory

When the network is unavailable, collected data will be temporarily cached in this directory. Once the network is restored, cached data is read from this directory and uploaded to the server.

This directory also stores temporary dump files generated by the javaagent memory dump feature.

Under normal circumstances, this directory does not occupy much disk space.

Directory	Linux	Windows
Application agent cache	~Number of agent instances * 100MB	~Number of agent instances * 100MB
machine	~100MB	~100MB
logsagent	~100MB	0
Total	~(Number of agent instances + 2) * 100MB	~(Number of agent instances + 1) * 100MB

---

Log Cleanup Policy

warning

This policy is not supported in serverless deployment mode.

The number of application agent logs increases with the restart of monitored applications. To prevent excessive disk usage, SmartAgent automatically cleans log files using a combined-condition strategy to maintain reasonable disk space.

• Space Limit: The total size of the logs directory and agentdumpproc directory are constrained; exceeding the limit triggers deletion (default 2GB each, total 4GB).
• Time Limit: Log files older than 14 days will be deleted.
• File Size Limit: Large individual log files are automatically cleared to prevent excessive resource usage.
• Count Limit: When the total number of files and subdirectories exceeds the limit, old files are deleted.
• Priority: Oldest files are deleted first.
• Special Rules:
  • Certain directories (e.g., machine, install, logsagent) are excluded (they have independent space limits and fewer files).
  • Coredump files are only cleared if older than 30 minutes (to avoid accidental deletion during analysis).
• Emergency Cleanup: If disk space is critically low, cleanup is triggered to free available space.