Apica LogFlow
  • Overview
  • EULA
    • End User License Agreement
  • Getting Started Guide
    • Deployment guides
  • Architecture
    • Never Block, Never Drop
    • InstaStore
    • Deployment
  • Flow Management
    • Overview
    • Forwarders
    • Mapping Applications
    • Data Transformation
  • Splunk Forwarding
    • Overview
    • Apica UF Proxy App Extension
      • Standalone Instance
      • List of Indexer instances
      • Indexer Discovery
    • Metric indexes
    • Non metric indexes
    • Syslog forwarding
  • Real-time Stream Forwarding
    • Overview
    • AWS Kinesis
    • Azure Eventhub
    • Google Pub/Sub
  • Forwarding To Data Warehouse
    • Overview
    • GCP Bigquery
  • Object Store Forwarding
    • Overview
    • S3 Compatible
    • Azure Blob Storage
  • Forwarding to monitoring tools
    • DataDog Forwarding
    • New Relic Forwarding
    • Dynatrace Forwarding
    • Elasticsearch Forwarding
    • Coralogix Forwarding
    • Azure Log Analytics Forwarding
    • JS Code Forwarding
  • Security Monitor Forwarding
    • Overview
    • Arc Sight
    • RSA New Witness
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. Splunk Forwarding

Non metric indexes

PreviousMetric indexesNextSyslog forwarding

Last updated 1 year ago

Was this helpful?

Apica supports forwarding to non-metrics indexes. Creating a splunk forwarder is straight forward and uses the "_json" type when creating the forwarder

The following formation is obtained from the Apica UF Proxy App extension for the forwarder

  1. The "Host" key is set to the Apica UF Proxy App extension that was created and should not use the Splunk host name.

  2. The "Password" is set to the hec_token from the Apica UF Proxy App extension

  3. The "Port" is set to 8088

  4. The "User" is set to "admin"

The Host, Password, Port, User can also be set to use an external Splunk HEC endpoint directly