About

The Local File NetoFuse module provides enriched asset context to Netography Fusion from a CSV or JSON file read from the local filesystem. It reads, transforms, and uploads Context Labels to the Netography Fusion API.

This may be used if you have a separate process that exports data to one of these formats and can save it to a filesystem. This can then handle converting that file to the appropriate Netography context label CSV format and automate the processing and uploading of that data.

The module will read files in a standard CSV or JSON format, using the file extension to determine the file type.

It supports defining a context transform to map fields to context label names and modify the values, just like other NetoFuse modules.

🛑

Using the NetoFuse upload command is usually the better option

To use the local file module, you will need to modify the configuration for the module and then run the module. You can bypass these steps by using the upload command instead. The upload command uses the localfile module to actually perform the work, so the results will be the same, but all the options are set on the command line instead of in a configuration file.

Other options for importing context labels from files

See the Generic Integration Capabilities for additional options for importing context.

Advanced configuration options

Multiple files can be imported with a single configuration, or you can use the advanced configuration to set multiple localfile module instances with unique transforms and settings. You may find that a single configuration file with multiple localfile instances and transforms defined is easier to manage than a script that executes multiple netofuse upload commands. Since upload acts as the command line front-end to configuring and running the localfile module, the end result will be the same.