Splunk On-Call
by Splunk (Cisco)
On-call scheduling and incident routing service, formerly VictorOps.
- Category
- IT, Security & Monitoring
- Type
- Incident management & On-call
- Interface
- REST API
- Built with
- Connect Any API
- Credentials
- API key
02Data
What you can sync.
- Incidents
- On-call schedules
- Teams
- Reports
Keep Splunk On-Call incidents in your own Lake, on your servers, and report on it with the rest of IT.
Need more? Name any other Splunk On-Call data the API returns, and the AI adds it to the connector.
03Credentials
Credentials you will need.
- An API key
Splunk On-Call uses an API key. You add the credentials once, when the AI asks for them, and it tells you where to create them in Splunk (Cisco) if you need help.
04How it works
How it works in DataMind.
-
Pick Splunk On-Call.
Open Lake, pick Splunk On-Call in the source picker and name the connection. Connect Any API opens with a ready prompt that points the AI at the Splunk On-Call API docs.
-
Answer a few questions.
The AI reads the Splunk On-Call documentation, then asks which credentials you will use, which data to sync (for example incidents and on-call schedules), whether you want a one-time load or a recurring sync, and which accounts or filters apply.
-
Your data lands in Lake.
It builds the connector, tests it and shows you sample rows. Then Splunk On-Call data loads into your Lake on your schedule, ready for the Warehouse, DataPrism BI and AI Minds.