Page created: 18 Nov 2021
|
Page updated: 9 Jan 2023
This section contains information for troubleshooting Splunk issues.
Issues with using Splunk to poll activity data from PingOne.
Index not populated
Getting too much data
activitiesRequestOptions
and add a filter parameter at
the end of the URI that meets your objective, such as:
uri:'https://api.pingone.com/v1/environments/066aaa70-37d4-43d0-9786-049e37b8aad1/activities?filter=createdat%20ge%20%22{lowerbound}%22%20and%20createdat%20le%20%22{upperbound}%22%20and%20action.type%20in%20(%22USER.CREATED%22%2C%22USER.UPDATED%22)&limit=500',
Not seeing status.json
STATUS_FILE
constant to point
to the appropriate location, such as: const STATUS_FILE =
"/Applications/Splunk/bin/scripts/tmp/status.json";
Getting duplicate events
| dedup id
function to manage
duplicates. Not running a local Splunk instance