Splunk APM Reviews

I have the logs of my applications, and they're usually a bit volatile. The log switch doesn't stay there on the application for a long time, so Splunk can require that. It can take 15 days for the logs to be available to do some kind of research. I'm using Splunk to ingest application logs, create dashboards, and set up alerts. 

The biggest benefit of Splunk is that we can retain logs and correlate the data. Telemetry data has a huge impact because it's much easier to see everything. 

Splunk has significantly reduced our mean resolution time. The workflow at my company involves application microservices applications running on the cloud. These logs are highly volatile, so they're only retained for three to five minutes, and we had to reproduce an issue to trace why it failed. That meant we had to do everything again to capture the log at the moment.  Now, we have the data to analyze one or two hours.

Splunk's dashboards are great. The solution provides end-to-end visibility across my environment. Visualizing large amounts of data is easier because we can correlate the data from any target source. 

The licensing model is expensive. We need to monitor the amount of data ingested because the cost is based on the data collected. 

I have used Splunk APM for three years now.

We have instances for production and development. I've never seen the production instance go down. Our development instance has gone down, but that's expected. 

I used tools like Elasticsearch, which is similar to Splunk. I've also used other observability tools like Grafana and Dynatrace, but they have different features.

I rate Splunk APM 10 out of 10.

We primarily use the solution for monitoring. 

The solution has a lot of features. 

It's a good traditional monitoring platform. 

The solution is stable and reliable. 

It can scale well. 

It's a little bit technical. 

The cardinality is pretty low. They need to expand their reach.

I've been using the solution for three or four years. 

The stability is good. I'd rate it eight out of ten. There are no bugs or glitches, and it doesn't crash or freeze. 

The scalability of the solution is pretty good. I'd rate the ability to expand at an eight out of ten. 

I'm not sure how many people are using the solution in our company. 

Technical support has not been an area of the solution I've dealt with. 

We previously used open-source solutions previously and found SignalFx to be better. 

I wasn't directly involved in the deployment of the solution. 

I have not looked into the ROI. I can't say if we have seen ROI or not. 

I haven't dealt with the pricing and licensing aspects of the solution. 

I don't know which version of the solution I'm using. 

I'd rate the solution seven out of ten overall. 

We use Splunk to monitor some devices in the company. We have several cloud groups for monitoring the energy companies in the state. The stack has several devices to monitor if you have a problem. There is a mixture of solutions.

The solution monitors the system in real-time. We can find the resources and investigate security incidents. Splunk and another solution, AppDynamics, monitor several devices.

We integrate Splunk with a data collection solution, and it plugs in the users to collect data at several points in the network and infrastructure. The data is indexed in Splunk, which can be visualized in different dashboards. Monitoring for fraud is critical for the company because you have to resolve many problems in the infrastructure with federal information in the dashboard. 

The company has many systems that the customer pays to access. Splunk APM issued via AppDynamics helps find problems in the feed. It reduces the risk of supervising all the devices. I can supervise the flow and simulate the conditions of the repository across several dashboards to show what's happening at the moment.

The dashboards are used mainly to visualize information about the infrastructure, but it isn't easy to construct or use the dashboards. While we tried to resolve the issue by calling support, it would be easier if they had an AI co-pilot to identify the problem and help you solve it. 

I have been using Splunk APM.

Splunk APM isn't easy to scale because you have to follow the steps and implement best practices, which can be a little awkward.

I rate Splunk support 10 out of 10. We had good documentation, and the support team at Splunk has a lot of experience with code and the tool. 

Positive

I haven't had any problems deploying Splunk. When I installed Splunk for the first time, I thought the product line was complex because I had to build the solution. After working on it for a while, it has become easier to do the solution next time.

Splunk APM is a crucial tool because it controls all the systems and solves a lot of problems.

I rate Splunk APM 8.5 out of 10. It's an excellent solution.

I use Splunk primarily from a gateway operations perspective. I work on application support. As part of that support, we regularly monitor the application dashboards built in Splunk using the logs. I covered this earlier this month.

The real problem we were facing was that we were unable to get all of our logs into a single place. We have an on-premise application with multiple servers across different data centers, and we needed to be able to view all of the logs together in order to troubleshoot any problems. That's why we started using Splunk to forward all of our logs to a single location.

Moreover, Splunk APM gives us end-to-end visibility across our entire on-premise environment. 

Another biggest benefit I've seen is the ability to quickly identify problems using Splunk alerting. We set up alerts against our application metrics, and this has helped us to resolve major issues much sooner. We can now identify problems as soon as they occur, which gives us time to take corrective action before they impact our users.

Splunk has reduced the amount of time our operations team spends investigating problems. This has freed up our engineers to focus on other tasks, such as improving our application performance and adding new features.

I like the fact that Splunk APM makes it easy to connect to the application database and run queries against the data. I also like the fact that Splunk APM allows me to use log forwarders to forward logs to a central location, where I can then build dashboards to view the data. The dashboards are probably my favorite feature of Splunk APM.

I've been using the Splunk query language, and it can be a bit time-consuming to set up the queries I need. I've had to look at a lot of community forums to find the filters I need, and it can be difficult to get the details I need.

I have experience building dashboards and other things with Splunk APM.

I've been using Splunk APM for over a year now. As part of my job in application support, I regularly create and maintain dashboards for our applications using Splunk APM. I also use dashboards to create alerts based on certain metrics.

Moreover, I'm currently working on a project to create a new dashboard for our customer support application.

The stability of the solution is good because I have never had outages I have seen so far. In terms of usage, it's good in terms of availability.

I haven't had to contact the support yet. We have a separate team that maintains and builds our relationship with Splunk, so they would be the ones to contact if we had any issues.

The solution doesn't require any maintenance. 

We used New Relic and AppDynamics before Splunk. AppDynamics was our APM tool, and I'm still using New Relic for monitoring Splunk. New Relic is great for log monitoring, and it's our main tool for internal application monitoring.

With Splunk APM as an enterprise solution, various factors come into play. Right now, considerations include pricing and how they envision the solution to work for them. Some might want the solution to be cloud-based. It largely depends on the volumes they anticipate. Organizations must decide how much they're willing to invest, especially when comparing it to other investments they've made. With the current economic recession and organizations looking to cut costs, it's crucial to evaluate the volumes and aspects of Splunk that are most relevant to them.

Overall, I would rate the solution an eight out of ten. 

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.

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 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.

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.