Splunk Infrastructure Monitoring

Formerly SignalFx

From my experience, everything related to infrastructure and application monitoring is perfect. Especially the monitoring, related to distributed tracing and mapping of the application relations and connections as part of the flow. Integration with AWS infrastructure is extremely good and very easy to be used. For the synthetic checks, [Splunk Infrastructure Monitoring (formerly SignalFx) is] less useful and appropriate.

Splunk Infrastructure Monitoring provides an excellent support experience for customers, offering a range of resources to ensure that users get the most out of their monitoring solution. The support team is knowledgeable and responsive, providing quick and effective assistance to resolve any issues that may arise.One of the key strengths of Splunk Infrastructure Monitoring support is the extensive documentation and online resources available to customers. The Splunk documentation library is comprehensive and well-organized, providing detailed information on every aspect of the product. In addition, the Splunk community is active and engaged, providing a wealth of user-generated content, including tips, tricks, and best practices for using the product.In addition to the extensive documentation and community resources, Splunk Infrastructure Monitoring provides a range of support options to meet the needs of different customers. These include email and phone support, as well as a web-based support portal where customers can submit and track support requests. The support team is responsive and knowledgeable, providing timely and effective assistance to ensure that customers get the most out of their monitoring solution.

Overall, Splunk Infrastructure Monitoring is a comprehensive and highly usable monitoring and observability solution. The platform offers a range of features and capabilities that make it easy for users to gain real-time visibility into the health and performance of their systems.

Monitor our application usage and system load.

Suitable for multiple AWS accounts / AWS services
EKS troubleshooting

This product is well suited for monitoring your infrastructure in a large way. I would say that this tool could be used in any size environment. I think this is a very well-rounded tool that could use some improvements but overall has many use cases and is stable enough to where you can use this well in production environments.

We used to use a lot of SQL logs and manual monitoring of our infrastructure. This takes time as well as being proactive to stay ahead of an outage no matter the severity. SQL logs are great but do take time to run. Manual checking is good for smaller networks or occasionally monitoring situations. As an organization, we were mostly reactive as it was nearly impossible to stay ahead of all negative situations. Splunk Infrastructure Monitoring has allowed us to become proactive, and freed us from manually looking for a fix or what the impact would be. It's all laid out for you and allows you to reach out to all necessary departments quickly. No more guessing!

Splunk Infrastructure Monitoring is well suited for any complicated environment where you have apps and servers across multiple clouds and platforms and products.

If you have a data centre where all your apps and servers are in one single network, you could probably get away with older solutions. But for any modern, complex, hybrid-cloud microservices environment, Splunk Infrastructure Monitoring is a must-have.

One of our best experiences has been Database monitoring as a derived service of APM. The ability to see the impact of poor queries without having to depend on Database-specific monitors is excellent. Another experience was the ability to determine the status of on-prem hosts via detectors and detector health-check. We use the health check to determine the host was unavailable in a 10-minute window which enabled our teams to take action and reduce the impact on the overall service.

I find that learning the interface can take some time. We need a better show-and-tell on how the Teams pages, Dashboard Groups, Dashboards and charts delay.

Advance SignalFlow is sometimes hard to build. Some better samples of advanced SignalFlow would be helpful. For example, Splunk SPL has a vast resource of examples.

Splunk Infrastructure Monitoring is really well suited for an enterprise that needs to monitor a large number of endpoints or transactions. Splunk excels at ingesting, storing, and aggregating data. This enables a company to trend its data over time, analyze it, and find trends and patterns in the data. It may not be ideal in a smaller environment with few endpoints or a minimal number of transactions. It can bring quite a bit of value but this needs to be weighed against infrastructure, license, and usage costs.

it is well suited to view complicated technical environments. We are working remotely but are still quite distributed, so it's important for us to all understand how we support each other.

Logs for all are appliances servers application access

mid-scale organizations should definitely leverage to automate and focus on critical business needs. Smaller organizations may use custom tools and solutions. It may not be cost-effective from what we have seen in our experience.

Data aggregation in the once account for all the customers and various service providers. I don't have to switch to different accounts which is really time-saving.

SignalFx makes it easy to visualize and alert on time series data. If you want to make charts of system load, requests per second, and so on, they will likely serve you well.

Splunk Infrastructure Monitoring will help in managing multi-cloud environments and in situations with speed and advanced analytics by monitoring and troubleshooting regularly for all the updates and risks. We found the product incredibly useful in giving us deep insights into what is happening within our environment.

Splunk Infrastructure Monitoring is the ultimate choice for infrastructure monitoring and can be easily mastered by the operations team. It even has built-in integration options support for various clouds and database or analytics services so it is the ideal choice for large enterprises to improvise observability and track key infra metrics. Newly they have introduced cloud SaaS service as well with easier pricing options to get started or evaluation.

Splunk Infrastructure Monitoring is well suited for scenarios where you have a large and well-expanded infrastructure for your applications and services. It helps to automate the monitoring process with zero human intervention. Easy integration with the cloud allows to performing monitoring at ease.

Classic monitoring of services vs. working without the need to implement an agent or code in your system

Error detection, outage detection, throughput monitoring, percentage monitoring are the scenarios that we’re currently using [Splunk Infrastructure Monitoring (formerly SignalFx)] for and they are well suited. I believe it is less appropriate when a precise number is required for monitoring. Because sometimes discrepancies occur because of metric collectors. For example, 100 metric is reported at time t, but on the charts, it’s split as 60 for time t and 40 for t1.

If you have a lot of traffic/users and you would like to monitor for some issues or bottleneck that might arise due to it [Splunk Infrastructure Monitoring (formerly SignalFx)] can really help you with.
If you find yourself repeating some math over and over just to extract interesting information from your product the try it out.

For monitoring cloud resources, such as instances, containers, pods, CPU utilization and the like, Splunk Infrastructure Monitoring [(formerly SignalFx)] is very well suited. For instantaneous notifications for events that require intervention, it is also pretty well suited. I'd say it is less appropriate for logging though, whereby historical data is used to trace bugs and issues in code.

It would probably work much better for static servers, not ephemeral VMs like EC2 instances.

SignalFX is well suited for environments where cost is a concern and the ability to decide what metrics are important to control that cost. Organizations with bandwidth to onboard a new system are also at an advantage. Organizations where cost is not a concern, may find better solutions elsewhere.