When assessing the two solutions, reviewers found AWS Cost and Usage Report easier to use and do business with overall. However, reviewers preferred the ease of set up with Splunk Enterprise, along with administration.
It breaks down expenses very well. The graphs and the data exports are pretty good.
I dislike how it is hard to tell what category spending falls under - such as AWS credit eligible costs.
Splunk is a fantastic tool that we depend on. It isn't just development work we rely on Splunk for, but we also use it for testing engineering changes as a standard before production releases. From ease-of-use, forwarding data from a variety of data...
I dislike the query language. I never found it intuitive. I felt it is reinventing the wheel, in a bad way. Also it is far from realtime when there is a lot of data. We have got to as much as 30 minutes delay in seeing the service is having a major problem.
It breaks down expenses very well. The graphs and the data exports are pretty good.
Splunk is a fantastic tool that we depend on. It isn't just development work we rely on Splunk for, but we also use it for testing engineering changes as a standard before production releases. From ease-of-use, forwarding data from a variety of data...
I dislike how it is hard to tell what category spending falls under - such as AWS credit eligible costs.
I dislike the query language. I never found it intuitive. I felt it is reinventing the wheel, in a bad way. Also it is far from realtime when there is a lot of data. We have got to as much as 30 minutes delay in seeing the service is having a major problem.