hi Splunk community,
Somehow my left join is not working if I select all EntityIDs.
Althought when I select a single IdentityId, it is working...
Any hints on why the first one is not working and how I can fix it?
Thanks,
Zarrukh
Since you have 500k events, JOIN command doesn't work as it is limited to 50k events. Try the following:
1. Write the data from the first search before JOIN command in your query to a lookup file (data_lookup_1.csv),
2. Write the data from the sub search to another lookup file (data_lookup_2.csv),
Your final query:
| inputlookup data_lookup_1.csv
| lookup data_lookup_2.csv EntityId
Try it and let me know if it works.
Thanks, that is what I was thinking about. 2 questions
1. How I can create and write the results into that csv file?
2. How I can setup automatic update of that csv file?
Thanks
1. How I can create and write the results into that csv file?
2. How I can setup automatic update of that csv file?
Have you considered using stats instead of join to avoid limits (you have half a million entity ids!)
how I can use that?
I would probably start like this
index="almost_a_hero_analytics"
| bin span=1d _time
| eval first_login=if(EventName="player_created", _time, null)
| eventstats values(first_login) as first_login by EntityId
| stats values(first_login) as first_login by _time EntityId
| eval datediff=max(round((_time-first_login)/86400,0),0)
| fieldformat first_login=strftime(first_login, "%Y-%m-%d")
| table _time EntityId first_login datediff
no, it will not work as it will take only people who created accounts for the selected time, but I need the list of accounts created for the whole time
Good point - you could create a summary index which collects player creation dates, then use a map command to search this index for the player creation date - you would need to set the maxsearches so that it covers the number of players in your time period. You don't have to use a summary index, it is just that it might be quicker. If you are doing this in a dashboard, you might be able to have an initial search (either of your whole data set or the summary index) which gets all the players creation dates, and load the results from this in the map search.