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
  • Command Line Options
  • Generate Support Bundle By Endpoint
  • Examples
  1. Additional Guides

Generating A Support Bundle

The Support Bundle feature allows you to generate a compressed tarball containing relevant data (logs, configs, and metric data) for troubleshooting or analysis. These bundled files can then be sent to the ElastiFlow support team to help diagnose issues with the collector. To use the Support Bundle command line tool, run the flowcoll command with the --support-bundle or -s flag. When the command runs successfully, it will produce a compressed tarball named similarly to ef_support_bundle-20230831T164759.tar.gz.

Basic Example:

./flowcoll -s

Advanced Example:

./flowcoll -s -sc /my/config/dir -sl /my/log/dir -st 3 -si 3000

Command Line Options

If an option is not specified, its specified default value will be used.

Option
Shorthand
Default Value
Description

--support-bundle

-s

false

Enables support bundle mode.

--support-bundle-config-dir

-sc

/etc/elastiflow/flowcoll

The path to the collector's configuration directory.

--support-bundle-logs-dir

-sl

/var/log/elastiflow/flowcoll

The path to the collector's log directory.

--support-bundle-metrics-interval

-si

1000

The interval, in milliseconds, at which metrics should be collected.

--support-bundle-metrics-times

-st

1

The number of times metrics should be collected.

--support-bundle-output

-so

<Working directory>

The path to which the output file should be written.

:::note By adjusting the collection interval (-si) and times (st), tracking and spotting trends in metrics over time can be easier. :::

Generate Support Bundle By Endpoint

HTTP Method

POST

URL

/support-bundle

Request Body

All fields in the request body are optional. Defaults will be used if not specified.

  • logDirPath (string): Directory path of the log files. Default: /var/log/juniper/flowcoll.

  • configDirPath (string): Directory path of the configuration file. Default: /etc/juniper.

Query Parameters

  • interval (integer): Interval at which the metrics will be fetched in milliseconds. Default: 1000.

  • times (integer): The number of times the metrics endpoint will be fetched. Default: 1.

:::note By adjusting the collection interval (-si) and times (st), tracking and spotting trends in metrics over time can be easier. :::

Authentication

This endpoint supports Basic Authentication only if the collector is specifically configured for it. For configuration details, see the API reference.

Examples

Basic Example

Using the defaults, this example demonstrates a basic example without any query parameters or request body.

curl -X POST \
  -H "Content-Type: application/json" \
  -O -J \
  http://localhost:8080/support-bundle

Advanced Example

This example demonstrates an advanced curl request with a filled request body and query parameters.

curl -X POST \
  -H "Content-Type: application/json" \
  -d '{
    "logDirPath": "/path/to/log/dir",
    "configDirPath": "/path/to/log/dir"
  }' \
  -O -J \
  http://localhost:8080/support-bundle?interval=2000&times=2

Responses

Code
Reason
Description

200

OK

Successful response will return the support bundle file for download. The file will have a naming convention ef_support_bundle-YYYYMMDDTHHmmss.tar.gz, where YYYYMMDDTHHmmss is a timestamp indicating when the bundle was created.

400

Bad Request

Query parameters are invalid.

500

Internal Server Error

An internal server error occurred while processing the request.

PreviousSNMP Device Support OverviewNextFAQ