Example scripts have arguments which make assumptions that sensors are accessed via SensorFleet Fleet Management
API documentation for the components is bundled with the exporter. URL paths to APIs are given in the form of /component/endpoint but in actual production deployments the API endpoint may be like https://xxx.yyy/instrument-uis/netflow_0@sensorname/endpoint which is reflected in the example scripts.
The long production-like full API endpoint URL is shortened for readability reasons.