Hi. We have a use case where we would like to maintain a single information field on some of our entities. The field name is Application Service, and it is fairly static - but not quite, so it might change over time. This field can logically only have one value, and the problem with the scheduled import, is, that if the value changes, there will be two values for this field name. So we are trying to create a Python script, that will maintain this value, so if it changes the still will only be one value - the old one is overwritten.  The problem is that when we try to change this vallue and posts to Splunk, we get a code 200 returnkode, but the value has not changed.   This is an example code: (Please don't kill me, this is just a test, and I'm not really a Python developer)   def update_splunk_rest(key, jsonDict): url = base_url + "/servicesNS/nobody/SA-ITOA/itoa_interface/entity/" + key + "?is_partial_data=0" authHeader = {'Authorization': token} r = requests.post(url, headers=authHeader, json=jsonDict, verify=False) print(r.text) return r splk_entity = get_splunk_rest("2b4566fb-367e-44ec-b068-d6541a2024e6") print(splk_entity.status_code) entity = splk_entity.json() print(entity) title = entity['title'] info = entity['informational'] print(info) keys = info['fields'] values = info['values'] print(keys) print(values) i=0 for field in keys: if field == 'Application Service': break i=i+1 values[i] = "Dette er Las test" print("=============================================================") print(entity) #payload = {"_key":"821bd2f7-83d6-47a9-a753-60c04523d57e","title":title,"informational":{"fields":keys, "values":values}} #print(payload) response = update_splunk_rest("2b4566fb-367e-44ec-b068-d6541a2024e6", entity) print(response.status_code)   The entity is changed just before the post (update_splunk_rest), that does a post with is_partiel_data=0, as we are changing the entire record from ITSI. Has anyone else had this problem and found a solution? Kind regards Las ... View more

Hi. I would like to import the services defined in our CMDB as ITSI Services. It seems that you have to set a specific team when you do the import, and for my trial it created duplicate services, if the service was defined in another team, than the one I specified at load time. I could the create an import for each team, but it seems quite cumbersome, when I can get the team in the data I get from the CMDB, so I would really like to know, if anybody has tried and found a solution, where you are not hard defining the team, but use values or even the team id from ITSI to create the services in one go?   KIind regards las ... View more

Hi. We are going to have a datasource with some sensitive data, where there is a requirement, that only the owner of a specific event is allowed to see it. The events will have the user as part of the data, that field can be created as an indexed field. I will, of course, have the data in a separate index, and thought I might be able to use restriction to limit access so that the user only can search in data where the field user matches the logged on user. I can see it is possible to use the token $env.user$ in a dashboard, but I would really like to use it in the restrictions part of the role, so it automatically will use the logged on user in the restriction.   Any help will be much appreciated. Kind regards las   ... View more

Hi. We have some IBM DB2 systems running primarily on AIX and now our Security team has tasked us with collecting the audit log in Splunk. I tried just creating an input, monitor-stanza pointing it to the right directory, but nothing, I then changed to look at subfolders, and I got some data. I have looked at the DB2 documentation, and there is a very cumbersome process described (https://www.ibm.com/docs/en/db2/11.1?topic=facility-storage-analysis-audit-logs). Does anybody have some experience collecting DB2 audit logs and how did you do it (file monitor or DB-Connect)?   Kind regards las ... View more

Hi. I would like to know if anybode else had this issue. We upgraded our UF on AIX to 8.1.3 from 8.0.4, following the guidelines from Splunk. We have set outputs.conf to use indexer discovery. After the upgrade we saw these message: ERROR IndexerDiscoveryHeartbeatThread - Error in Indexer Discovery communication. Verify that the pass4SymmKey set under [indexer_discovery:prod] in 'outputs.conf' matches the same setting under [indexer_discovery] in 'server.conf' on the Cluster Master. [uri=https://xxxx:8089/services/indexer_discovery http_code=502 http_response="OK"] The pass4SymmKey has not changed during the upgrade. We changed the configuration to bypass indexer discovery, and that got data flowing into the system again.   Kind regards Lars Søndergaard ... View more