Skip to main content

Quick Start

UniAgent Deployment (Linux Only)​

When there are applications in multiple languages on a Linux server, it is recommended to use UniAgent for installation.

The installation path is fixed at /opt/tingyun-oneagent. For installation steps, please refer to UniAgent Deployment Guide.

The UniAgent package integrates Agents for Java/PHP/.NET Core/Node.js/Python. After installation, you do not need to manually modify the application's configuration files. All Agent embedding actions are automatically completed by UniAgent, and it can automatically monitor applications inside Docker containers.

After UniAgent installation is complete, if you need to monitor Python applications, you need to manually enable the Python monitoring switch in /opt/tingyun-oneagent/conf/interceptor.conf by setting python_enabled=true.

sudo sed -i -e "s/python_enabled.*/python_enabled=true/" /opt/tingyun-oneagent/conf/interceptor.conf

Then restart the Python application.

Standard Deployment (Linux Only)​

The following quick installation steps are performed in the command line, using a Django application as an example.

  1. Extract the Agent installation package.

    tar -zxvf tingyun-1.1.0.tar.gz -C /tmp

  2. Install the Agent.

    python /tmp/tingyun-1.1.0/setup.py install

  3. Generate the local configuration file.

    tingyun-admin generate-config  YourLicenseKey outputFile.ini

    Example:

    tingyun-admin generate-config 123-456-789-001 /tmp/tingyun.ini

  4. Open the local configuration file, set collectors, and set ssl to False.

    The format is collectors=IP:Port. For example:

    collectors=10.128.1.12:7665

  5. Deploy the Agent.

    Assuming the configuration file is stored at /tmp/tingyun.ini, configure as follows:

    TINGYUN_CONFIG_FILE=/tmp/tingyun.ini tingyun-admin run-program <application start command> <application start parameters>

    Example:

    TINGYUN_CONFIG_FILE=/tmp/tingyun.ini tingyun-admin run-program python manage.py runserver

  6. Access the application.

    The Agent requires application access to drive the Agent to work. Please access the application after deployment.