All Apps and Add-ons

Elastic Search Data Integrator - Using index patterns as indices ?

welo78
Explorer

Hello all, we have a problem that our Splunk's Elastic Search Integrator addon is using a forbidenn character inside it's Splunk index due to connecting to a "frontend" cluster. Let me explain.

The problem is that they have a “frontend” cluster which uses index patterns to search between clusters. This is also the cluster which’s endpoint is connected to our Elasticsearch Data Integrator app for Splunk. The “backend” cluster is the one containing our index.

So the infrastructe is like this:

Cluster Backend > Cluster Frontend > Splunk’s addon

Backend’s Cluster index: security-audit-XXX

Frontend’s cluster index pattern: *:security-audit-*

As it is stated in Elastic's documentation here, the use of colon (:) inside index is forbidden. However we are using it and index pattern. Does anybody have any suggestions how to tackle this ?

Labels (3)
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Data Outage Monitoring and Reporting

We’ve all been there, right? Living our best life, working on our Splunk environment, when out of nowhere a ...

Manage Datasets and Connections in Catalog on Splunk Cloud Platform

Set Up Data Where You Use It Catalog already helps teams find and understand data across Splunk indexes, ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...