We use tracking cookies to understand how you use the product and help us improve it. Please accept cookies to help us improve. You can always opt out later via the link in the footer.
Non-invasive account access for better security and efficiency.
Import data with CloudQuery SDKs and build your own plugins.
Query cloud assets and security with a simple SQL-based UI.
To install CloudQuery, run the following command in your terminal:
brew install cloudquery/tap/cloudquery
Next, run the following command to initialize a sync configuration file for ServiceNow to Splunk:
cloudquery init --source=servicenow --destination=splunk
This will generate a config file named servicenow_to_splunk.yaml. Follow the instructions to fill out the necessary fields to authenticate against your own environment.
Next, log in to the CloudQuery CLI. If you have't already, you can sign up for a free account as part of this step:
cloudquery login
cloudquery sync servicenow_to_splunk.yaml
This will start syncing data from the ServiceNow API to your Splunk database! 🚀
See the CloudQuery documentation portal for more deployment guides, options and further tips.
append
write mode, this means that it will not remove data from your Splunk destination and will create new indexes when needed.batch_size
, batch_size_bytes
, and max_concurrent_requests
integers. In general, you should keep the max_concurrent_requests
integer as low as possible while aiming for a ratio of roughly 1,000 between batch_size
and max_concurrent_requests
, this will ensure that the response times from your Splunk instance remain reasonable.