Source without an add-on
Bring in a proprietary application or a SaaS service.
Digital Engineering & Automation
Bespoke add-ons, inputs, commands and connections to bring data into Splunk and trigger actions outside it.
Not every source has a Splunkbase add-on, and not every alert should stay inside Splunk: sometimes it needs to open a ticket, call an API or enrich an event with external data.
Five phases, always in the same order. Select each one to see what happens in it. In full projects they map onto the stages of our method.
We understand the process, the systems involved, the constraints and how success will be measured.
We design the solution: components, interfaces, security, error handling and deployment.
We develop the add-on, input, command or action using Splunk's official frameworks.
We validate the package with AppInspect and test it in a Splunk environment before installing it in production.
We measure actual usage, fix issues and document so your team can maintain it.
Bring in a proprietary application or a SaaS service.
Open a ticket or notify another tool.
Add external data to events at search time.
Yes, we validate the apps with AppInspect so Splunk Cloud accepts them.
Yes, such as the Splunk Add-on UCC Framework and the Splunk SDK for Python.
We also integrate with its API to automate detectors, dashboards and data.
Tell us about your situation. If this service is not what you need, we will tell you; if it is, we will propose a concrete first step.
Request this service