VMRAY Connector
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.


Carbon Black - VmRay Connector

Installation Quickstart

As root on your Carbon Black or other RPM based 64-bit Linux distribution server:

cd /etc/yum.repos.d
curl -O https://opensource.carbonblack.com/release/x86_64/CbOpenSource.repo
yum install python-cb-vmray-connector

Once the software is installed via YUM, copy the /etc/cb/integrations/vmray/connector.conf.example file to /etc/cb/integrations/vmray/connector.conf. Edit this file and place your Carbon Black API key into the carbonblack_server_token variable and your Carbon Black server's base URL into the carbonblack_server_url variable.

To start the service, run service cb-vmray-connector start as root. Any errors will be logged into /var/log/cb/integrations/vmray/vmray.log.


If you suspect a problem, please first look at the vmray connector logs found here: /var/log/cb/integrations/vmray/vmray.log (There might be multiple files as the logger "rolls over" when the log file hits a certain size).

If you want to re-run the analysis across your binaries:

  1. Stop the service: service cb-vmray-connector stop
  2. Remove the database file: rm /usr/share/cb/integrations/vmray/db/sqlite.db
  3. Remove the feed from your Cb server's Threat Intelligence page
  4. Restart the service: service cb-vmray-connector start

Contacting Carbon Black Developer Relations Support

Web: https://developer.carbonblack.com E-mail: dev-support@carbonblack.com

Reporting Problems

When you contact Carbon Black Developer Relations Technical Support with an issue, please provide the following:

  • Your name, company name, telephone number, and e-mail address
  • Product name/version, CB Server version, CB Sensor version
  • Hardware configuration of the Carbon Black Server or computer (processor, memory, and RAM)
  • For documentation issues, specify the version of the manual you are using.
  • Action causing the problem, error message returned, and event log output (as appropriate)
  • Problem severity