[ 
https://issues.apache.org/jira/browse/METRON-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16881113#comment-16881113
 ] 

Simon Elliston Ball commented on METRON-2178:
---------------------------------------------

This question really belongs on [the 
us...@metron.apache.org|mailto:the%c2%a0us...@metron.apache.org] list. What you 
need to do is use the tenant field from your key (I'm assuming you are using 
the mergeMetadata or readMetadata methods) to build the index pattern 
expression in your indexing config to route differently based on the tenant 
data.

On a side note, you should consolidate your NiFi flows and use the attributed 
expression language there to avoid creating too many NiFi processors (you only 
need one PublishKafka)

> Can two user access different data in one index at ElasticSearch after Apache 
> Metron Indexing?
> ----------------------------------------------------------------------------------------------
>
>                 Key: METRON-2178
>                 URL: https://issues.apache.org/jira/browse/METRON-2178
>             Project: Metron
>          Issue Type: Task
>    Affects Versions: 0.7.1
>            Reporter: Rendiyono Wahyu Saputro
>            Priority: Minor
>              Labels: beginner, features
>         Attachments: rendi.png
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Good Morning,
>  Hi everyone
> Right now, i use two ( 2 ) TailFile on Squid Log in Apache Nifi. Each one, 
> connected to separated two ( 2 ) PutKafka with different Kafka Key but using 
> one Topic name.
> And the end, Apache Metron save indices to ElasticSearch as one ( 1 ) index.
> The question is, how can different user ( User A and User B ) to access 
> different Squid Log ( using metadata / Kafka Key ) in one ( 1 ) index.
> I want to accomplish this, because this is much efficient to parser different 
> data source using one ( 1 ) sensor. Can you help me or give a guidance about 
> this ?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to