![]() ![]() Therefore building a generic Splunk Modular Input for polling data from any REST API is the perfect solution. As our esteemed Ninja once said, “Data First, Sexy Next”.Īnd I want to make it as easy, simple and intuitive as possible to allow you to hook Splunk into your REST endpoints, get that data, and starting writing searches. I am most interested in the “getting data in” part of the Splunk equation. The REST “dataverse” is vast, but I think you get the point. What type of data is available ? Well here is a very brief list that came to mind as I typed : I see a world of data out there available via REST that can be brought into Splunk, correlated and enriched against your existing data, or used for entirely new uses cases that you might conceive of once you see what is available and where your data might take you. And of course, Splunk has it’s own REST API also. It is simple, lightweight, platform independent,language interoperable and re-uses HTTP constructs. REST really has emerged over previous architectural approaches as the defacto standard for building and exposing web APIs to enable third partys to hook into your data and functionality. More and more products,services and platforms these days are exposing their data and functionality via RESTful APIs. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |