Which firewall ports do I have to open for the Quanta agent?
For the agent to work you must allow outgoing HTTPS connections to our IPs (IP range 22.214.171.124/27).
To install the packets you must also allow your server to connect by HTTP to apt.quanta.gr
You can also implement a HTTP proxy if your server doesn't have direct access to the internet. You can add your proxy's URL in the configuration of the agent (/etc/quanta/agent.yml) by adding a line in the following format "proxy_url: http://user:email@example.com" under the category "server".
I don't see the data, where can I find the information to solve the problem?
The agent uses syslog to generate logs, you will generally find them in the file /var/log/daemon.log or /var/log/syslog. If you don't find the source of the error, you are welcome to contact us.
You can send logs to another file by replacing the variable file in the section logger in the file /etc/quanta/agent.yml (do not forget to setup a logrotate process).
I'm running Varnish on my server and I installed the Varnish agent but I cannot see the data in Quanta, how do I fix this ?
You're probably using a non-default Varnish nstance (it means you're using the "-n <your_instance_name>"
flag to run Varnish and in your varnish monitoring tools such as varnishstat).
If you're in this configuration, you'll need to specify the "-n" parameter in the Quanta configuration file as well (/etc/quanta/modules.d/varnish.yml):
I run multiple instances of Memcached, Redis or Varnish on my server, is it possible to monitor all of them ?
Yes, it is possible starting from version 1.1.0 of Quanta agent.
You'll need to specify a different configuration file for each instance in the directory /etc/quanta/modules.d/. For instance, if you wish to monitor 2 different Redis instances (one for the sessions store which runs on port 6379 and another one to store some cache which runs on port 6378), you might setup this 2 files:
This configuration will work the same way for Memcached and Redis, except you'll have to replace the configuration key "redis" as well as the parameter "module" (used to let Quanta agent which module should be loaded).
Is it possible to monitor services that are not on the same machine?
We recommend installing the agent on all your servers, however if you can't on some of them (database for example) and you still want to monitor the MySQL service, you can change the setting host in the configuration of the agent (/etc/quanta/modules.d/<service>.yml)
I already installed the Zabbix agent beforehand, how do I update it?
The update is done automatically during the installation of the Quanta agent. We stop requesting the Zabbix agent as soon as we receive the metrics of the new agent.
You can verify that your server is relaying the data correctly via the new agent by checking the presence of the flag "New agent" in the configuration of your servers in Quanta.
Once you have validated that the metrics are relayed correctly via the new agent, you can completely uninstall Zabbix.
I already installed the Magento module beforehand, how do I update it?
The update is done automatically. We stop requesting the old Magento module as soon as we receive the first metrics from the new PHP extension.
If a scenario is using the new PHP module correctly, you will see a "New module" flag.
We recommend uninstalling the old module when the new one is installed.
Do I need to create my server in Quanta?
No, creation is automatic and is done once we receive the data. If your server already existed in Quanta its configuration will be automatically updated.
You will, however, have to delete the server from Quanta manually if you remove it from your infrastructure.
I am concerned about the security of my server, can you explain to me in a little more detail how the Quanta agent and the PHP module work?
We are just as concerned as you are about the safety of the tools we offer you, here is a technical description of how they work.
All packages we provide are signed with a GPG key that you need to install in your package system to verify the origin of these packages.
The Quanta agent is a service that runs in the background on your server (daemon) and performs several operations:
- Collection of system data via reading of files in /proc.
- Collection of data on the active services of your server (Apache, Nginx, Varnish, Memcached, Redis, MySQL), usually via a connection to the service. In any case, it is never necessary to create a privileged user for the agent to access this data.
- Receipt of PHP module data via a Unix socket (rights can be configured if necessary)
- Sending the collected data to Quanta via the secure HTTPS protocol (it is possible to use a proxy if necessary).
All Quanta Agent modules can be disabled independently if you wish.
The agent starts as root for its initialization phase (opening its socket, loading the configuration, etc.) but changes to standard user for all collection operations (user and group are configurable).
The data collected by the agent is stored in memory before being sent to Quanta but never stored elsewhere.
The PHP module:
The PHP module is a PHP extension (in the form of a dynamic library) which will be loaded by PHP when running PHP on your server.
It collects its data only:
- When you perform actions in your back office
- During requests made by our probes (identified via a particular header in the request)
The module does not alter the functioning of the application, it simply retrieves various profiling information on the functioning of Magento.
The module also has an "xhprof" mode (complete profiling of the execution), which works on the same principle but is never activated by Quanta without user action.
The data is transmitted to the agent via the Unix socket provided for this purpose and will never be stored or sent anywhere else.
If you have any further specific questions, please do not hesitate to contact support on this subject, we will be happy to answer you.