Splunk APM Reviews

I am a technology analyst. I have been working on a financial project in the US. For this project, I used Splunk APM for troubleshooting and reviewing the logs, and finding errors. Most of our APIs ran on Splunk APM, and we used it to find errors in our production environment.

We are no longer using Splunk APM. We have switched to Dynatrace.

Splunk APM is very good for monitoring purposes. You can watch application-to-application flows. If you just click on a flow, you can go step by step and debug an issue. The places with errors are marked in red. The API or the application in which you are getting an error is red. From there, you can go to the log or the error, and then the person responsible for that particular API or application has to fix it.

Splunk APM gives tools for user monitoring, logs observability, infrastructure monitoring, synthetic monitoring, and automated on-call. 

Splunk APM provides real-time data. In the logs, if you want to see errors related to status 404, you can just write one keyword, and you will get the results.

Splunk APM offers end-to-end visibility across the environment, but it also depends on how your business is set up on Splunk APM.

Splunk APM helped to reduce our mean time to resolve (MTTR). Previously, I had to log into my VPN, run commands, and see the logs. After having Splunk APM, I could click on one link and go through the logs. 

We could set up Splunk APM based on our environment. I worked on one project with Splunk APM. In that project, we faced a lot of issues, and I resolved the issues with the help of Splunk APM. I found the accurate logs and the easiest way to resolve the errors.

Splunk APM is the most advanced application for performance monitoring and troubleshooting for cloud-native applications and microservices.

The ability to troubleshoot is valuable. While running any product or API, we need to troubleshoot issues. We need to find the error in the logs. In Splunk APM, we have the section logs. In that section, we can search with any particular keywords. Before Splunk APM, I also worked with Splunk Enterprise where we have various dashboards to monitor. 

It is an application performance monitoring and observability tool. It is a very good tool. You need to use the documentation on Splunk's website. From there, you can learn many things. I have Splunk certification. You can dive deep into it. For me, it gives end-to-end visibility into our production environment.

They can improve the flow system and the keyword language. It has predefined keywords, but they can be improved. I also use LogMeIn where I can use predefined keywords to see the logs. 

They should give us the option to use our own language to search. For example, I should be able to search for an ID name along with an error or status code. 

I worked with Splunk APM for one and a half years.

I have not faced any downtime. I have worked with Splunk APM for one and a half years, and I did not face any downtime during this duration of time.

I have never faced any issues with scalability.

I did not have any need to contact support because I did not face any issues. 

We used another solution previously. In Splunk Enterprise, it is easier to create dashboards. You can easily set up application alerts and infra alerts. You can search with metrics and you can set alerts based on a specific error. Whenever that error occurs, you will receive an alert.

I am not involved in its deployment. In terms of maintenance, it is owned and managed by Splunk. Everything is maintained by Splunk. I have not faced any downtime with Splunk APM. I have also used Splunk Enterprise previously. With both of these products, I did not face any downtime. 

The pricing is reasonable.

It is a good tool. It allows you to set alerts for application and infrastructure monitoring, and it allows you to create dashboards. You can set alerts based on the threshold or traffic.

For logging purposes, Splunk APM is very good, but we should be able to use our own search query language. Currently, we can only search based on the predefined tags.

Overall, I would rate Splunk APM a nine out of ten.

I am using Slunk APM mostly for telemetry and logs.

The Slunk APM proves to be extremely useful for troubleshooting production issues. We rely heavily on its detectors to monitor the traffic flow between microservices, and any sudden deviations in traffic, whether due to errors or changes in inflow, trigger alerts. This allows us to quickly investigate the source of the traffic and identify bottlenecks in the microservice ecosystem. once we have a problem, we are looking through the logs, and it has really helpful filters. We are able to find what we want quickly.

When an issue arises, we search through the logs using the highly effective filters that are provided. This enables us to quickly locate the required information with ease.

The most beneficial aspect of Slunk APM is the ATM, which is the map displaying the inbound and outbound relationships of the microservices, as well as the traffic between these dependencies. This feature provides us with valuable insights and helps us understand the interactions between different microservices.

Primarily, the logs in Slunk APM can be challenging to navigate and comprehend, making it difficult to understand the details within each log. Compared to other tools like LogDNA, which are more intuitive in this aspect, the logs in Slunk APM can require more effort to understand.

It would be beneficial to have a feature that addresses the scaling of microservices. At times, issues with microservices may not be related to the code, but rather to the available resources. Therefore, it would be useful to have a feature that indicates the status of the microservices, including their scaling status and any relationship between the two.

I have been using Slunk APM for approximately one year.

The metrics in Slunk APM may not always be accurate as they depend on the computer generating the report. If the reporting machine is underperforming, it can show lower metrics, which can be misleading. Therefore, it's important to be cautious when relying solely on Slunk APM for accurate metrics.

I rate the scalability of Slunk APM an eight out of ten.

The scalability of the solution is good.

We plan to increase our usage because new features of the solution are coming out.

I rate the scalability of Slunk APM an eight out of ten.

I have not used the support. I did not have any problems.

I have previously used LogDNA for logs and Newrelic for telemetry .

The initial setup of Slunk APM was straightforward.

We have received a return on investment after switching from our previous solution to Slunk APM.

The price of Slunk APM is less than some of its competitors.

We choose Slunk APM over other solutions because of the cost benefits.

If you're planning to use Slunk APM, my suggestion is to exercise caution, especially if the machines you're using are under heavy load with graphics or other resource-intensive tasks. In such scenarios, the data you get from Slunk APM may not be entirely reliable. Nonetheless, it's an excellent tool that can provide a comprehensive overview of your system if you integrate it into all aspects of your operations. With Slunk APM, you can easily identify bottlenecks and improve your programs, making it an incredibly useful tool.

I rate Slunk APM an eight out of ten.

Right now, I am using the infrastructure monitoring module. It's mostly for monitoring the infrastructure workloads. We can monitor our server, database and networks. It's mostly metric-based monitoring. 

The time to go live is very fast. It takes mere minutes for the sys admin to set up the solution.

The features are pretty much ready out of the box. 

The visualization is very user-friendly.

It is stable.

The solution scales well.

The pricing is very reasonable. 

We can't really configure the solution. 

The UI enhancements could be a way to improve the solution in the future. 

We'd like the solution to be better integrated with Splunk Cloud. 

I've used the solution for almost a year. I haven't used it for that long.

The solution is pretty stable. There are no bugs or glitches. It doesn't crash or freeze. It is reliable. 

This is a very scalable solution. You can have different deployment modules. It's flexible. 

I've never contacted technical support. We don't take care of that aspect of the product. 

This offers a very easy setup.

The deployment is fast. It was very quick. It does depend on how fast your infrastructure is. 

The solution is reasonably priced compared to the competition. We do not find it very expensive at all. 

I'm an end-user and customer.

We're using the SaaS deployment. We don't have visibility into the version number. 

I'd recommend the solution. We've had a good experience firsthand. It's a very simple solution to grasp and understand from an end-user perspective. You just might need a bot of configuration to visualize the data. 

I'd rate the solution nine out of ten. 

I primarily use Splunk APM for logging and metrics.

Splunk APM has helped us to standardize logging and monitoring procedures. 

Splunk APM's most valuable feature is the application performance monitor.

Splunk APM's performance could be improved - at the moment, it's very slow and takes forever to give me what I want. Its documentation and accessibility to end-users could also be better.

I've been using Splunk APM for a year and a half.

I would rate Splunk APM five or six out of ten for stability.

Splunk APM scales well.

I would give Splunk APM a rating of four out of ten.

We use this solution to monitor all our FaaS workloads.

This solution is very quick to deploy as it is a SaaS solution and integrates with tools like ServiceNow.

The monitoring of workloads when using SignalFx could be improved. 

We have used this solution for more than 20 years. 

This is a stable solution. 

This is a scalable solution. 

We have received good technical support when needed. 

Positive

I would rate this solution an eight out of ten.