Data transparancy is one of the key drivers of Rumble development. We do our best to ensure that any data gathered, transmitted, or downloaded is easy to view, import, export, and reprocess. Data generated by the Rumble Agent can be downloaded and reprocessed by the Rumble Scanner. Raw data from the Rumble Scanner can be imported into the Rumble Console. This data is consistently formatted and almost always backwards compatible between versions.

Rumble Scanner Data

This week we released version 1.3.1 of the Rumble Scanner, which adds even more features for working with data and bringing that data back into the cloud console. The new additions include:

  • Support for the --baseline option, which accepts an assets.jsonl file from a previous run, or a JSONL export from the Rumble Console, and uses this as a baseline for normalizing and deduplicating assets. Assets matched against the baseline will carry forward the same UUID values, as well as tags and comments, in the resulting assets.jsonl of the new scan. For folks who primarily use the Scanner (and our OEM integrators), this simplifies the process of asset tracking between scans, allowing the same logic as the cloud backend to be applied to local scan data.

  • Support for the --upload option. The Rumble Scanner can now upload data directly to the cloud console. If you want more flexibility for how scans are run, when they are run, and from what systems, the Scanner can now be used as a primary driver of scan data for the console. To use this option, specify an Organization API key for the --api-key parameter and optionally, set the --upload-site name to the Site to populate. If you want to send data to your own endpoint, you can override the --api-host parameter and build your own handler for the Import API.

  • Support for multiple --import options. This change allows the Rumble Scanner to consolidate raw scan data (scan.rumble or the raw task data from the console) into a single output. This works with the --baseline option to track and correlate assets and with the --upload option. The import option works with or without new scan parameters. If you would like to import one more previous scans into a remote site, specify each --import file, set the --api-key, and an optional --upload-site.

If you haven’t had a chance to try the Rumble Scanner yet, you can sign up for a free trial and then download the binary for your platform of choice from the Scanner section of the console. For additional information about the Scanner, including the command-line options, take a look at the documentation. We hope you find these additions useful and would love your feedback about what we can do to make Rumble work even better for your use case.

Happy scanning!

-HD

Similar Content

Scanning & Searching Version 1.5.0 of Rumble Network Discovery is live with updates in two major areas; wider scanning, through improved protocol support, scan engine enhancements, and more comprehensive decoders; and deeper searching, with the addition of a dozen new search filters and other enhancements to the web console. Wider Scanning Whether you use the Rumble Agent or the Rumble Scanner, the scan engine improvements in v1.5.0 make discovery more reliable, predictable, and comprehensive.
Version 1.3.0 of Rumble Network Discovery is now live with a new Organization API, support for the BACnet protocol, tons of new fingerprints, and improvements across the Rumble Console user interface. If you haven’t had a chance to try Rumble before, or would like to play with the new features, sign up for a free trial and let us know what you think! Organization API Rumble now supports a REST API tied to Organization-specific API keys.
After announcing v1.1.5 with the new Switch Topology report, quite a few folks wrote in to ask if this feature was available in SNMPv3 environments. As of this evening, the answer is yes. To leverage SNMP v3 credentials in a Rumble scan, set the following options in the Advanced Options section of the Scan Configuration screen. Depending on your environment, these settings may require some tweaking. The standard security levels of NoAuthNoPriv, AuthNoPriv, and AuthPriv map to these options as follows: