First of all, I love the community team and everyone within the community! Awesome work everyone!! Also, if there are badges being handed out for helping, could it be added to this user and not my cmerriman_splunk user? This is the one I use for community 🙂 Thanks 🙂  ... View more

That's a good catch @black_bagel , but you don't have to eval domain_all before you do the foreach statement, you could just have |makeresults | eval domain_field1=1| eval domain_field2=5| eval domain_field3=4| eval domain_field4=6|foreach domain_* [|eval domain_all=min(domain_all,'<<FIELD>>')] and that will still produce 1 for domain_all. ... View more

Here is a good start for a rest call: |rest splunk_server=local servicesNS/-/-/data/ui/views f=eai:* f=label f=title  the field eai:acl.owner will give you the owner of a dashboard.  REST Splunk Doc  I'm not sure that I 100% understand your use case, though. You have a dashboard (or dashboards) that you want to send a PDF of to a dynamic list of users, and the results of the dashboard should change based on the recipient? Or did I completely miss the use case ... View more

I'm not sure if this solved the original issue but it definitely has been a great solution to my issue 🙂  ... View more

Here's a starting off point. This likely needs some adjustments but should get you going.   index=_audit search="'search *" sourcetype=audittrail|stats values(apiStartTime) as earliest_time by search_id search|rex field=search max_match=0 "\'search\s.*index=(?<searched_index>[^\s|\"]+)"|rex field=search max_match=0 "\'search\s.*\`(?<macros_used>[^\`]+)\`"|rex field=search max_match=0 "\'search\s.*eventtype=(?<searched_eventtype>[^\s|\"]+)"|join searched_eventtype splunk_server type=left [|rest /servicesNS/-/-/admin/eventtypes splunk_server=* f=search f=title|table splunk_server title search|rename title as searched_eventtype search as searched_eventtype_def]|join macros_used splunk_server type=left [| rest /servicesNS/-/-/admin/macros splunk_server=* f=definition f=title|table splunk_server title definition|rename title as macros_used definition as macro_used_def]|rex field=macro_used_def max_match=0 "index=(?<macro_index>[^\s|\"]+)"|rex field=searched_eventtype_def max_match=0 "index=(?<eventtype_index>[^\s|\"]+)"|eval all_searches_indexes=coalesce(searched_index,coalesce(macro_index,eventtype_index))|eval all_searches_indexes=if(isnull(all_searches_indexes),"not_defined or *",all_searches_indexes)|stats values(earliest_time) as earliest_time by search_id all_searches_indexes|eval earliest_time_epoch=if(earliest_time="'ZERO_TIME'",relative_time(now(),"-90d"),strptime(earliest_time,"'%a %b %d %T %Y'"))|eval earliest_time_bucket=case(earliest_time_epoch<relative_time(now(),"-7d"),"last 7d",earliest_time_epoch<relative_time(now(),"-14d"),"last 14d",earliest_time_epoch<relative_time(now(),"-21d"),"last 21d",earliest_time_epoch<relative_time(now(),"-28d"),"last 28d",1=1,"last 90d")|chart count by all_searches_indexes earliest_time_bucket   What this is doing is looking at audit logs for any search being run. Then using regex, it's extracting anything with index= to grab the indexes. It's also looking for any macros or eventtypes so that it can grab any of those that might have indexes defined in them. You might want to tweak that bit a little to search for just eventtypes with indexes and macros with indexes. Then it joins them all together into one field and grabs the earliest time for each search and buckets the time by your definition above. ... View more

Do different lines of the alert get sent to different recipients? Or is it just that one copy of the alert get sent internally and one copy of the exact same dataset get sent externally? ... View more

Is the regex101 what you want extracted? all those groups? or is it not exactly what you want? what is the limit problem? is this a regex you're doing in props or transforms or are you doing it with |rex on the search line? can you provide the entire stanza or the entire search string? ... View more

Good point @MuS ! Thanks! ... View more

In Splunk v 7.3+, you can use the rest call, as long as your lookup tables have definitions in transforms.conf created. | rest splunk_server=* /servicesNS/-/-/data/transforms/lookups getsize=true f=size f=title f=type f=filename f=eai*|fields splunk_server filename title type size eai:appName |where isnotnull(size)|eval MB = round(size / 1024 / 1024, 2)|search MB>{0}|fields - size The docs do not have the getsize param defined yet, but there has been feedback submitted to have it added. ... View more

Are timezones an issue for this search? You could just create an eval statement that says if _time is between certain hours to mark it as one time period, and so on. ... View more

Just to verify - the alert is enabled? When you run that search over 15 minutes, you get data? (I'd hope so since it's _internal) Did you check the _internal scheduler logs to see if there was any error for this search? Skips or anything ... View more

I haven't done this in a while, so it might not be true for v8*, however I recall in v6* there was an issue with schedule PDFs that took too long to run. The PDF would render empty panels if the search ran for an extended period of time. How long does your search typically take to run? Found the doc on this: https://docs.splunk.com/Documentation/Splunk/8.0.2/Viz/DashboardPDFs#Configure_the_timeout_setting_for_generating_a_PDF default is 1h in limits.conf, not sure if your env. has the default limit or another limit set. Something you could look into to see if that's the reason? ... View more

do you have valid creds? the last line mention that the authorization failed and to verify the username and password for the api. ... View more

Thanks @woodcock try this query: | rest splunk_server=* /servicesNS/-/-/saved/searches f=title f=eai:acl* f=description f=qualifiedSearch f=next_scheduled_time search="eai:acl.app!=splunk_archiver" search="eai:acl.app!=splunk_app_windows_infrastructure" search="eai:acl.app!=splunk_app_aws" search="eai:acl.app!=nmon" | table splunk_server title, eai:acl.owner, description, eai:acl.app, qualifiedSearch, next_scheduled_time | search next_scheduled_time!="" qualifiedSearch!="*index IN*" | regex qualifiedSearch!=".*index\s*(!?)=\s*([^*]|\*\S+)" | regex qualifiedSearch="^\s*search " | regex qualifiedSearch!="^\s*search\s*\[\s*\|\s*inputlookup" | rex field=qualifiedSearch "^(?P<exampleQueryToDetermineIndexes>[^\|]+)" |rex field=exampleQueryToDetermineIndexes max_match=0 "eventtype=(?<eventtype>[^\s]+)" |join eventtype splunk_server type=left [|rest /services/admin/eventtypes splunk_server=* f=search f=title|table splunk_server title search|rename title as eventtype search as eventtype_def] |eval eventtype="eventtype=".eventtype|eval exampleQueryToDetermineIndexes=if(like(exampleQueryToDetermineIndexes,"%eventtype%"),replace(exampleQueryToDetermineIndexes,eventtype,eventtype_def),exampleQueryToDetermineIndexes) |replace *eventtype* with *eventtype_def* in exampleQueryToDetermineIndexes | regex exampleQueryToDetermineIndexes!="\`" | regex exampleQueryToDetermineIndexes!=".*index\s*(!?)=\s*([^*]|\*\S+)" | regex exampleQueryToDetermineIndexes!=".*tag\s*(!?)=\s*([^*]|\*\S+)" |where isnotnull(exampleQueryToDetermineIndexes) |fields - eventtype eventtype_def | rename eai:acl.owner AS owner, eai:acl.app AS Application |stats values(*) as * by Application title It actually comes from https://splunkbase.splunk.com/app/3796/ , if I recall correctly - we adjusted it slightly in our environment, but I think this is the original search. ... View more

you need to create two tokens, one fore ANI and one for CASE_NUMBER something like <set token="case_num">$row.CASE_NUMBER$</set> <set token="ani">$row.ANI$</set> and then edit the search drilldown to use those two tokens. something like <link target="_blank">search?q=<search in url encoded nonsense>&amp;CASE_NUMBER=$case_num$&amp;ANI=$ani$</link> ... View more

It's not the No Title that's taking up space, it's the html break that you have. you might be able to use some CSS to reduce the space, but I don't have any written up that'll help at the moment. ... View more

base searches do not work like that. you can't add it as an identifier inside of a search string, it only works inside of the node. You'll probably want to use |loadjob create a token with the sid from your base search, something like <done> <set token="sid">$job.sid$</set> </done> and then within your subsearch, something like |loadjob $sid$..... ... View more

Just want to double check one thing: you used your jira service account and api token, as well as your jira site url, for the configs? Not just your jira username/password? ... View more

so.... snow_index has taskcurrentstatus: "TASK0001OpenService - Tools" snow_index_2 has taskcurrentstatus: "TASK0001OpenService & Tools" You can't just join on taskcurrentstatus and expect it to match those two together, because they don't match. you'd need to do something like: |replace "* - *" with "* & *" in group before you eval taskcurrentstatus and a similar one in the subsearch with t_group but really, you shouldn't use join, it's ugly and has limitations. try something like this: (index=snow_index sourcetype=task_lookup_dat_csv) OR (index=snow_index_2) | eval ExistingInSummaryTable=if(index=snow_index,"No","Yes") | eval taskcurrentstatus=coalesce(number+state+group,t_number+t_state+t_group) | stats values(t_number) as t_number values(t_state) as t_state values(t_group) as t_group values(ExistingInSummaryTable) as ExistingInSummaryTable by taskcurrentstatus| search ExistingInSummaryTable="No" you might need to adjust that a bit, break it apart command by command, but you can do that search without a join, guarantee it. ... View more