This January, we introduce the 1st round towards a better way to manage your fleet of kproxy agents.
You can deploy kproxy agents to secure the network telemetry data between your own devices and Kentik's public Flow/SNMP/BGP ingest front-doors, configuring your routing gear to ship this data to a kproxy instance in your network, which will relay the resulting multiplex securely to Kentik's SaaS Clusters.
More information about kproxy here in our knowledge base.

Kproxy is now a first-class citizen in the portal, i.e. it comes with its own Settings screen. This screen comes with the following elements:

• Ability to name and locate your agents in sites that you've configured for other routing devices, and set flow listening IP (mostly useful for config snippets)
• 
• A new onboarding path that will let users deploy a kproxy instance in the first touch experience as a first step in the flow-generating device provisioning first touch onboarding flow.
  
  • The onboarding flow, as well as the modal from the Flow Proxy Agent screen in Settings now displays updated instructions to deploy kproxy both in an ad-hoc manner as well as using the industry-standard systemd service manager.
• The updated deployment method for kproxy now alleviates the need for user-specific API credentials to launch a kproxy instance. Company-global credentials are provided in the instructions, whether in onboarding or on the kproxy settings screen.
• Multiple screens in the existing Kentik UI have been updated to reflect a flow device’s dependency on kproxy as follows:
  • The Network Explorer Device Details page, in the “More Info” section
  • The Settings > Device page with its device details drawer
    
    

Note that existing kproxy-based users will see their kproxies show up in the UI without the site, name and IP metadata associated with them. These can freely be updated as suggested by the UI.