Skip to main content

Frequently Asked Questions

Troubleshooting​

No Log Output​

Description: No agent log is generated, or there is no log output in the log file. Alternatively, only the message "agent check logfile config input message" appears (generated by the tingyun-admin check-config command), with no other log entries.

Solution:

  1. Install the agent in the same Python environment as the user application. The agent must be in the same environment to function. Pay special attention if using a virtual environment.
  2. Set read permissions for the agent configuration file. The Linux user running the application process must have read access to the agent configuration; otherwise, the agent may not be able to read it due to permission issues.
  3. Set appropriate write permissions for the log file specified in the configuration file. The user running the application must have write access to the agent log; otherwise, no log will be generated.

Only Agent Initialization Log​

Description: The agent log only contains initialization log entries (as shown in the example below), but there is no subsequent data reporting or other log output, even though data appears in the dashboard.

Solution:

After the user application starts, the Python logging module is configured with the parameter disable_existing_loggers=True, which disables third-party log output. Alternatively, the agent log is initialized first by the Python logging module, and then the monitored application calls logging.config.fileConfig().

In this case, simply set the disable_existing_loggers parameter to False in the Python logging configuration.

Q&A​

Q: Why does updating the local configuration not take effect?​

A: If you update the local configuration file, the agent system cannot automatically detect the change. The current solution is to restart the application (which will also restart the agent).

Q: How can I verify whether the agent configuration file and options are correct and reasonable?​

A: We provide a command-line tool tingyun-admin check-config to check the configuration file. It can check for common option errors, but cannot verify license validity.