Data Center Real-User Monitoring (DCRUM), discontinued vs. Splunk Observability Cloud

Dynatrace Network Application Monitoring (NAM), formerly DCRUM, has improved greatly compared to when it was DCRUM; however, it still needs a lot of improvement in end-to-end flow capture with regards to network monitoring. Its alerting and integration capabilities are very good and easy to use. But it still needs a lot of tweaking in usability.

Incentivized

Good for below cases 1. There is a front end and need to correlate data with front end data 2. multiple microservices and need to check the health of each system 3. correlate data from various sources 4. Application performance is a key to be captured 5. application performance is a key metric.

Incentivized

• Dynatrace Network Application Monitoring (NAM), formerly DCRUM, is very useful to find the network packet flow across applications
• It shows the application behavior in terms of end-user performance
• It integrates very well with other Dynatrace components

Incentivized

• The first one is its Kubernetes container monitoring.
• I really like this features because as we know how much K8s is vast and to manually monitor each part of the Kubernetes it takes so much time but Splunk Observability Cloud makes it easier. And even once we integrate K8s with Splunk Observability Cloud it gives us some prebuilt dashboards which gives holistic view of our Cluster and its nodes, pods, etc.
• The dashbaord feature of Splunk Observability Cloud, it gives us full flexibility to customize our dashboard with a wide range of predefined chart types.
• Now it also supports OTEL, which is a plus point for observability. As now everyone is moving towards Otel and in current market there are only few tools who supports OTEL based integrations, Splunk Observability Cloud is one out of them.

Incentivized

• Its configuration requires a lot of technical and business knowledge to drive monitoring expectations to dashboards.
• DCRUM needs a robust monitoring architecture to store, analyze and visualize all collected data.
• DCRUM can't monitor the latest Microsoft Exchange versions.

• An indicator for errors on the navigations pane so that we don't have to go through each tab.
• As we go more and more cloud maybe you guys can implement a pay-as-you-use strategy so that small companies using it not frequently can also afford it.
• That's it can't think of any and it wont let me skip to next question. Thanks

Incentivized

Good: Stable system with low error rate Easy to use for simple use cases Bad: UI is not very clear for complex usage Mobile view (when logged in from phone) is bad No library for .net

Incentivized

Best of breed.

Overall a great tool to have in your toolbox, It is very intuitive and our entire staff uses the tool. It is easy to use and cost is very reasonable. Splunk also has excellent support team and very easy to work with. Every time we had a challenge, support team was able to help us with the end result.

Incentivized

The only thing missing for a 10, would be if they texted or called you back.

Splunk support is very quick and efficient. Pre-sale specialists are very skilled and available.

Incentivized

Follow a training before starting.

Incentivized

Nagios can't trace real user transactions from a front-end tier through a backend-tier,;with Nagios you only can monitor server availability and hardware issues. Riverbed is commonly used to determine networking issues without considering real user transactions impact on an application stack.

To be honest, Datadog is very similar to Splunk and LogScale to a lesser degree, but it is just as good if you don't need too complex observability. Grafana is still growing and might reach the same level soon.

Incentivized

• It has reduced the number of war rooms as well as the number of people involved to address issues.
• It helps in utilization trending for network capacity.
• It has prevented poor solutions from hitting production.
• When the various business units launch own initiatives such as third party tools or new platforms, it's become extremly easy to detect.
• The reports help in the field of continuous improvement as any changes are immediately discovered and can be compared to history. Deviations from what you have decided as a tolerance corridor can be used to trigger alarms, both positive and negative.

• Significantly reduced the MTTR (Mean Time To Recovery), which in turn has improved the end-user experience tremendously.
• Meets compliance requirements of security policies, audit, regulation, and forensics.
• Helps us to track/manage the resource usage on our cloud instances which has a direct implication on the recurring cost.

Incentivized