Zenoss

1. Open the config file, which is located at /etc/bigpanda/bigpanda.conf.

2. Locate the settings for the Zenoss full sync, named zenoss/fullsync.

3. Change the value of the full_sync_interval to your preferred interval between full syncs, in seconds. The default value is 900 (15 minutes).

1. Open the config file, which is located at /etc/bigpanda/bigpanda.conf.

2. Locate the settings for the Zenoss full sync, named zenoss/fullsync.

3. Add the following key and value pair: "enabled": false.

1. Stop the BigPanda agent by running the following command.

   sudo service bigpanda stop

2. Remove the integration from the agent configuration file by running the following command. Replace the app key with the corresponding value in BigPanda.

   sudo bigpanda-config -r <INTEGRATION APP KEY>

3. Start the BigPanda agent by running the following command.

   sudo service bigpanda start

1. Ensure python3 is installed with the following command:

   $ sudo apt install -y python3

2. Verify the install with the following commands:

   $ python3 --version
   $ pip3 --version

Connect to a host that can access the API endpoints and install the BigPanda agent package.

1. Ensure packages are installed prior to downloading the BigPanda agent package:

   $ sudo apt update && sudo apt install -y gnupg2 curl lsb-release

2. Add the BigPanda repository and download the OpenPGP key:

   $ echo deb https://bigpandaio.jfrog.io/artifactory/int-deb `lsb_release -c -s` main | sudo tee /etc/apt/sources.list.d/bigpanda.list
   $ curl -sL https://bigpandaio.jfrog.io/artifactory/api/security/keypair/bigpanda/public | gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/bigpanda.gpg > /dev/null

   • The --dearmor option is for unpacking input from an OpenPGP ASCII armored key.

   • Since apt-key is marked to be deprecated on future releases of Debian and Ubuntu, it is preferred to manage keyring files in trusted.gpg.d instead.

   • Note: apt-key can still be used in place of OpenPGP, but it is less secure.

     $ curl -sL https://bigpandaio.jfrog.io/artifactory/api/security/keypair/bigpanda/public | sudo apt-key add -

4. Update the repo list and install the BigPanda agent package.

   $ sudo apt update
   $ sudo apt install -y bigpanda-agent

   Note: For the OIM, bigpanda-agent v10.0.0+ is required.

1. Follow the Docker Installation Guide for your system.

2. If using Docker Compose, follow the Install Docker Compose guide to ensure the latest version of compose is installed on your system.

   • Docker Compose is built with the latest version of Docker Desktop.

   • If using Docker CLI, ensure Docker CLI's Compose Plugin is installed separately.

1. Pull the latest BigPanda agent docker image from the BigPanda JFrog Docker Registry:

    docker pull bigpandaio-int-docker.jfrog.io/bigpanda-agent:latest
   

2. Check that the latest image was downloaded successfully:

    docker image ls
   

1. Run the container in detached mode, passing both BP_TOKEN and ZENOSS_APP_KEY environment variables to docker run.

    docker run -dit \
    --name bp_agent \
    -e BP_TOKEN=<Your Org Bearer Token> \
    -e ZENOSS_APP_KEY=<Your App Key> \
    bigpandaio-int-docker.jfrog.io/bigpanda-agent:latest
   

2. View the logs of the running docker container:

    docker container logs -f bp_agent
   

1. Create a file called docker-compose.yml:

   vim docker-compose.yml

2. Add the BigPanda agent service configuration to docker-compose.yml:

    version: '3.9'
    services:
      bp_agent:
        image: bigpandaio-int-docker.jfrog.io/bigpanda-agent:latest
        container_name: bp_agent
        restart: always
        stdin_open: true
        tty: true
        environment:
          - BP_TOKEN=<Your Org Bearer Token>
          - ZENOSS_APP_KEY=<Your App Key>
        networks:
          - bigpanda
   
    networks:
      bigpanda:
        external: true

   It's important to note that the following commands are based on having Docker Engine 19+ installed, or Docker Desktop installed which has Docker Compose support. If the docker-compose plugin is installed separately, then the command will start with docker-compose vs docker compose.

3. Bring up the agent container:

   docker compose up -d

   -d is used to run the container in detached mode.

4. View the logs of the running docker container:

   docker compose logs -f

5. You can bring down the container with the down command:

   docker compose down

1. Attach to the shell session to continue setting up Zenoss

   docker attach --detach-keys="ctrl-q" agent

   Since ctrl-c will send a kill signal to the shell, stopping the container, --detach-keys passes an alternate key sequence.