Agent Service Deployment¶
Obsy Agent Teams supports self-hosted operation. The Agent's runtime service can be deployed on local hosts, virtual machines, or your team's own infrastructure, allowing you to control the runtime environment, network access, permission policies, and dependency management.
Install Agent Service¶
After creating an Agent, the system generates an installation command exclusive to that Agent. You can complete the deployment by following these steps:
- Navigate to the Installation Command or Run & Deploy section of the current Agent.
- Select the target host operating system.
- Choose whether to enable "Agent Self-Observability Collection". When enabled, the workspace will receive and display observable data from the Agent's runtime process.
- Copy the installation command from the page.
- Execute the installation command on the target host or virtual machine.
- Wait for the installation to complete; the Agent will automatically connect to the current workspace.
- Return to Obsy Agent Teams to check the Agent's status.
Note
The installation command is only for the current Agent and should not be forwarded to unauthorized personnel. If the installation command or credentials are leaked, please contact the administrator promptly.
Runtime Status¶
After installation, you can view the service status on the Agent dashboard. If the status is abnormal, it is recommended to first check:
- Whether the target host can access the Obsy Agent Teams service.
- Whether the installation command originates from the current Agent.
- Whether host time, network proxy, or firewall policies affect the connection.
- Whether the runtime service is blocked by system security policies, process management tools, or container policies.
- Whether related credentials have expired, been revoked, or reset after a leak.
Deployment Recommendations¶
- Deploy the Agent in an environment that can access the target tools and data sources.
- For Agents related to production environments, prioritize using controlled hosts or team-managed virtual machines.
- Provide installation commands, API Keys, platform credentials, secrets, and Tokens only to authorized personnel.
- If multiple Agents need to access different systems, it is recommended to separate deployment environments and network permissions by responsibility.
- Regularly check for unused Agent services and promptly deactivate or clean them up.