What do you like best?
The ability to use XML to create and style your own dashboards.
What do you dislike?
To get the most out of the app a lot of people with different skill sets need to be involved and with the same goal in mind, for example, the observability engineers are the ones in charge of the maintenance and setup of the Splunk platform and data, while the backend engineers are the ones that implement the logs caught by Splunk. The frontend engineers need to look into the available logs and see what information from there is useful to create a dashboard that can be used for ourselves or for the product owners.
Recommendations to others considering the product:
Great software that is useful for the entire engineering department. Is important that to extract the most value from this investment you must make a conscious effort to align and train employees with different skillsets to be able to get the most out of the dashboards, visualizations, data discovery, and alerts. Well used this can bring insights of your product from different perspectives, not only for data analytics but also for use cases such as measuring the feature adoption rate, this can help you tweak your UI to make sure you focus your engineering workforce on the modules and functionality that bring the most value to the users of your app.
What problems are you solving with the product? What benefits have you realized?
Measuring the adoption rate of new modules and features. Is very easy to see where our customers are finding more value from our products.