Some integrations require the BigPanda agent to send data to BigPanda. These integrations include Zabbix, Nagios, and Zenoss. Common questions include:
By default, the log files are located at
/var/log/bigpanda/. BigPanda log files are rotated when they reach 10MB and only 3 versions are stored at any given time. To change these settings, see Configuring the BigPanda Agent Logs.
Yes, we’ve designed the agent to be secure and non-intrusive. The installer uses signed
deb/rpm packages. The agent itself runs as a custom non-root user and it communicates with BigPanda via SSL.
In most cases, you need only one agent per master server of your integration. If you have multiple masters, you need to create a separate integration, using different app keys, for each master.
BigPanda does not miss alerts, even if your connection is down. The BigPanda agent intelligently retries sending your alerts, until it’s successful. Once the connection is revived, you will see the events in BigPanda.
Yes, see Using the BigPanda Agent with a DMZ.
No, each agent is assigned a unique "agent_id" value (found in the /etc/bigpanda/bigpanda.config file) and can only support one integration.
Use this procedure to debug the root cause of connectivity issues when configuring the agent behind a proxy. Connectivity issues are often manifested as connection errors inside the agent log file.
Agent version 2.11.2 and above.
SSH to the server on which the agent is installed.
Run the following command and save the output to a file.
bigpanda-check-proxy --proxy <proxy_url>
Run the following command and save the output to another file.
curl -v --proxy <proxy_url> "https://api.bigpanda.io/health/data"
Send the output from both commands to BigPanda support. We will work with you to troubleshoot common connectivity issues.
Updated 6 months ago