FAQs related to Docker application and Docker agent
What is the necessity to have an exclusive docker agent?
When changing from monolithic application deployments to cloud native microservices using AWS ECS, Kubernetes etc., an exclusive monitoring agent would prove to be more secure and flexible to keep track of your docker containers and hosts. Also, the agent follows the "container philosophy" i.e., any single active process is wrapped inside a container, thus making cluster management more easy.
- How does installation process vary between the docker agent and the Linux server moniotoring agent?
The docker agent, when executed, will create a container with the agent, that will monitor the underlying host. On the other hand, the docker application will be auto-discovered once the Linux server moniotoring agent is installed. - Are the docker agent and server monitoring agent different?
No, the method of installing the agent varies. It's the same agent installed either as the Linux agent or from the docker store as the docker agent. - When installed as an agent, will the server also be monitored?
Yes, once the docker agent is installed, a monitor will be created for the server and another monitor would be created for the docker. - Can the docker agent be installed in a machine, where there is already a Linux agent?
No, either the Linux or the Docker agent can run in a machine. - Will there be high memory and CPU usage because of the docker agent?
The docker agent needs a minimum of 256 Mi of CPU and 200 MB of memory. The user can also set limits as to how much memory and CPU should be consumed by the agent. - Will there be a change in the performance metrics while using the docker application and the docker agent?
No, the performance metrics will remain the same, except for disk related metrics. To get disk related metrics for the docker agent, mount the volumes into the container and get them monitored.
- Is there any licensing difference between the docker agent and the docker application?
No, there is no licensing difference. Irrespective of whether an application or agent, docker is a basic monitor. Any bulk installation techniques for the docker agent?
Are plugins and resource checks supported with the docker agent?
Note: For plugins, go to the respective container by using the following command:
docker exec -it site24x7-agent /bin/bash
Then, create a folder in /opt/site24x7/monagent/plugins/<foldername> and place your plugin script file in this folder.
Related Articles
Licensing for Docker (old)
This article contains the licensing model for the customers who signed up before August 2024. Check out this article for more information on the new licensing pattern. Note that the new licensing model applies to users who signed up after August ...
List of log files generated and maintained by the Site24x7 server monitoring agent
Here is the list of log files generated by the Linux and Windows server monitoring agent. The log files are stored in the same directory where the agent source file is installed. By default they are at: For Linux : ...
Adding a Python agent to a Python application service
To monitor a Python application using Site24x7 APM, you need to integrate the Site24x7 Python agent as a system service. Follow the steps below to install the S24x7DataExporter, add the agent to a custom directory, and configure the environment. ...
APM Insight agent log paths
Folder path to view One agent logs One agent logs can be found only in the common application folder in Windows (usually under C:\ProgramData from Vista onwards). Check the following folder path in Windows: C:\ProgramData\Site24x7APMOneAgent\Logs ...
How to add APM Insight Java agent without application restart?
In general, after installing the APM Insight Java agent, you have to restart your application for the agent to capture monitoring data. But in case of critical issues in the app, like sudden application slowness, where you haven't installed APM ...