Splunk for log collection, indexing, analysis & dashboarding
December 14, 2018
Splunk for log collection, indexing, analysis & dashboarding
Score 8 out of 10
Vetted Review
Verified User
Overall Satisfaction with Splunk Enterprise
Splunk is used in our enterprise to analyze monitoring and analytics data. We have thousands of micro services and APIs in our organization. All these APIs emit log data that is used to aggregate and analyze using Splunk. It also helps in end-to-end tracking of flows and data across services, in troubleshooting errors, and in generating metrics. Splunk is also used generating and configuring alerts.
Pros
- Used for indexing and collecting machine data and log data from APIs.
- This data is used to generate graphs, alerts, metrics that is useful to business, technology and operations.
- It is data source agnostic and is used to log API, batch, db and log data. It runs on AWS for us.
Cons
- The only con might be that it is much costlier than an open source system like ELK (Elastic Logstash Kibana).
- Splunk has been used as a one-stop-shop for log collection, indexing, alerting, analytics and dashboarding
- Splunk is a costly software however ROI on our engineering and operations is huge.
- Negative could only be its high licensing costs. It might not be a viable option for all companies.
We have also used ELK (Elastic Logstash Kibana) with some benefits, but Splunk is way better than ELK.
We also use AWS CloudWatch for Lambdas that are written in AWS. However CloudWatch is not a replacement for Splunk.
We also use AWS CloudWatch for Lambdas that are written in AWS. However CloudWatch is not a replacement for Splunk.
Comments
Please log in to join the conversation