Docs
test1test2
6.5
6.5
  • ElastiFlow Documentation
  • Unified Flow Collector
    • General Configuration
    • Changelog
    • Maxmind GeoIP2 and GeoLite2
    • RiskIQ PassiveTotal
    • Network Interfaces
    • User-Defined Metadata
    • Docker
    • Linux
    • Unified Flow Collector Introduction
    • System Requirements
    • Supported IEs
    • AWS VPC Flow Log IEs
    • IPFIX IEs
    • Netflow IEs
    • sFlow IEs
  • Unified SNMP Collector
    • Device Groups
    • Changelog
    • Devices
    • Downloading Definitions
    • Enumerations
    • Objects
    • Object Groups
    • User-Defined Metadata
    • Docker
    • Network Interfaces
    • United SNMP Collector Introduction
    • Linux
    • Scheduling Rediscovery
  • Monitoring ElastiFlow
    • Liveness & Readiness
    • Metrics
    • Prometheus & Grafana
  • Configuration Reference
    • YAML Configuration Files
    • Configuration Reference Overview
    • Common
      • API
      • Licensing
      • Overview
      • Logging
      • HTTP output
      • Elasticsearch output
      • Kafka output
      • Monitor output
      • OpenSearch output
      • Splunk output
      • stdout output
      • Processor
    • Unified Flow Collector
      • Overview
      • Community/Conversation IDs
      • EF_PROCESSOR_ENRICH_TOTALS_IF_NO_DELTAS
      • Overview
      • RiskIQ PassiveTotal
      • Maxmind
      • User-Defined Metadata
      • Overview
      • Overview
      • User-Defined Metadata
      • Overview
      • Benchmark Input
      • Netflow/IPFIX/sFlow (UDP)
      • Licensing
      • Decoder/Processor
      • Sample Rate
      • Configuration Changes
    • Unified SNMP Collector
      • User-Defined Metadata
      • Overview
      • Licensing
      • SNMP Poller
      • EF_PROCESSOR_SNMP_ENUM_DEFINITIONS_DIRECTORY_PATH
  • API Reference
    • API Reference Overview
    • SNMP Operations
  • Data Platforms
    • Elastic
      • Basic Cluster
      • Advanced Cluster
      • Single Server
      • Multi-Tier Cluster
      • Single "Lab" Server
      • Elasticsearch
      • ElastiFlow vs. Filebeat and Logstash
      • RHEL/CentOS
      • Ubuntu/Debian
      • Kibana
      • ML
        • Network Security
        • Machine Learning
        • Availability
          • Network Availability
          • DHCP
          • LDAP
          • DNS
          • NTP
          • RADIUS
          • TCP Sessions
        • Network Security Activity
          • Rare Autonomous System
          • Network Activity
          • Rare Conversation
          • Rare Geolocation
        • Network Security Brute Force
          • Brute Force CLI Access
          • Brute Force Remote Desktop Access
          • Brute Force Attacks
        • Network Security DDoS
          • Denial-of-Service
          • ICMP Flood Attack
          • SYN Flood Attack
          • TCP DDoS Attack
          • UDP Amplification Attack
        • Network Security Recon
          • ICMP Scan
          • Reconnaissance
          • Port Scan
        • Performance
          • Unusual ASN Traffic Volume
          • Unusual Network Interface Traffic Volume
          • Network Performance
    • Opensearch
      • Dashboards
      • Auth Sig V4
    • Splunk
      • Default Search Macro
      • Configuring Data Input & Index
      • Splunk App Installation
    • Output Configuration
  • Additional Guides
    • Catalyst (sFlow)
    • FortiGate
    • hsflowd
    • Configuring Flow Sampling on Juniper Routers
    • Junos OS (sFlow)
    • MikroTik RouterOS
    • OpenWRT (softflowd)
    • Ubiquiti EdgeRouter
    • SonicWall
    • Junos OS
    • Extending SNMP Device Support
    • Flow Device Support Overview
    • SNMP Device Support Overview
    • Generating A Support Bundle
  • FAQ
    • Flows stopped showing up in Kibana (Disk(s) Full)
    • Common reasons why you have discrepancies between ElastiFlow data & reality
    • What Are Snapshots?
    • Importing the wrong dashboards (No data)
  • Knowledge Base
    • Config
      • Elasticsearch Authentication Failure
      • CA Certificate Path Incorrect
      • license/error Invalid Segments
    • Flow
      • Bidirectional Flow Support
      • Configure the UDP Input
      • Flow Records Not Received
      • Netflow v9/IPFIX Template Not Receieved
      • Unsupported sFlow Structures
    • General
      • License Has Expired
      • License Agreement Not Accepted
    • Install
      • .deb Upgrade Fails File Overwrite
    • Operation
      • Flow Collector Queues 90% Full
      • Dashboard Updates
      • Change elastiflow-* Index Name?
  • Elastic Stack Deployment
  • Download Links
Powered by GitBook
On this page
  • Install hsflowd
  • Edit hsflowd configuration file
  • Configure sFlow settings
  • Save and exit
  • Restart hsflowd
  • Verify the configuration
  1. Additional Guides

hsflowd

PreviousFortiGateNextConfiguring Flow Sampling on Juniper Routers

hsflowd is an open-source host sFlow agent designed to monitor servers, virtual machines, and containers. It provides resource usage statistics, performance metrics, and network traffic data by leveraging the sFlow standard. Here's how to configure hsflowd:

Install hsflowd

First, you need to install the hsflowd package. The installation process varies depending on your operating system. For example, on a Debian-based system like Ubuntu, you can use the following commands:

sudo apt-get update
sudo apt-get install hsflowd

For other systems, you may need to download and compile the source code from the official GitHub repository:

Edit hsflowd configuration file

After installation, locate the hsflowd configuration file, typically found at /etc/hsflowd.conf. Open the file with a text editor of your choice, such as nano or vi.

sudo nano /etc/hsflowd.conf

Configure sFlow settings

In the configuration file, you'll find several settings that need to be configured, such as the collector's IP address, port, sampling rate, and polling intervals. The configuration file uses an XML-like syntax. Here's an example of a basic configuration:

<sFlow>
  <sFlowSettings>
    <sampling>400</sampling>
    <polling>20</polling>
    <header>128</header>
    <datagram>1400</datagram>
    <agent>AGENT_IP_ADDRESS</agent>
  </sFlowSettings>
  <collectors>
    <collector>
      <ip>x.x.x.x</ip>
      <udpport>6343</udpport>
    </collector>
  </collectors>
</sFlow>

Replace AGENT_IP_ADDRESS with the IP address of the sFlow agent (typically the host's IP address) and x.x.x.x with the IP address of your ElastiFlow Unified Flow Collector. You can adjust the sampling, polling, header, and datagram values as needed.

Save and exit

After configuring the sFlow settings, save and exit the configuration file.

Restart hsflowd

To apply the changes, restart the hsflowd service. The command varies depending on your operating system. For a Debian-based system like Ubuntu, use the following command:

sudo systemctl restart hsflowd

Verify the configuration

To verify that hsflowd is running and exporting sFlow data, use the following command:

sudo systemctl status hsflowd

This command should display the status of the hsflowd service, indicating it's running and active.

Once you've completed these steps, your server will start exporting sFlow data to the specified flow collector. Make sure your ElastiFlow Unified Flow Collector is set up to receive and process the exported data for analysis and monitoring purposes.

https://github.com/sflow/host-sflow