Splunk Search

why user with same role not able to see data

vikramyadav
Contributor

Hi Guys,

I have created a simple query with stats command and I'm able to see the required results.

If same search is ran by another user he is not able to see results but if that user removes commands from the search query he is able to see events.

I checked permission of that user and it have same roles which I have.

So I beleive it's not a permission issue.

Labels (2)
0 Karma
1 Solution

isoutamo
SplunkTrust
SplunkTrust
Can it be hat this error_id field is your own field extraction not shared within app or global level?

View solution in original post

isoutamo
SplunkTrust
SplunkTrust
Hi
can you post the query, description of environment (single node, shared environment etc.)?
r. Ismo
0 Karma

vikramyadav
Contributor

Hi @isoutamo,

It's a single node. Below is the search query which I'm using.

index=abc host=xyz "Error executed unexpected" | stats count(error_id) as error

If user is running whole seach query he is not able to see results where as if user is not using command he is able to see events.

0 Karma

isoutamo
SplunkTrust
SplunkTrust
Can it be hat this error_id field is your own field extraction not shared within app or global level?

vikramyadav
Contributor

thanks, @isoutamo  that worked.

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!

[Puzzles] Solve, Learn, Repeat: Character substitutions with Regular Expressions

This challenge was first posted on Slack #puzzles channelFor BORE at .conf23, we had a puzzle question which ...

Splunk Community Badges!

  Hey everyone! Ready to earn some serious bragging rights in the community? Along with our existing badges ...

[Puzzles] Solve, Learn, Repeat: Matching cron expressions

This puzzle (first published here) is based on matching timestamps to cron expressions.All the timestamps ...