Nexthink Workplace Experience is a cloud-native platform allowing IT teams to manage the Digital Employee Experience (DEX) by providing insights across devices, applications, users, operating systems, locations and organizational units.
N/A
Splunk Observability Cloud
Score 8.2 out of 10
N/A
Splunk Observability Cloud aims to enable operational agility and better customer experience through real-time AI-driven streaming analytics allowing accurate alerts in seconds. It is designed to shorten MTTD and MTTR by providing real-time visibility into cloud infrastructure and services.
I've been managing desktops for 20+ years and Nexthink was the missing tool out of my toolbox. Just to give some perspective, if you were building and maintaining a house, Nexthink would be comparable to switching up from a hammer and nails and to full blown using a nailgun. Nexthink is a solution accelerator and a well thought out toolset to give you the customer experience at a glance. It allows for so much more visibility just with the default set of data points the Collector (agent) gathers, which is A LOT, and grants you the ability to gather even more data with remote actions. All of this evidence cuts how the "it could possibly be this" and "maybe it's that" discussions when you're troubleshooting an issue. It may not provide the exact answer all the time, but it gives you a "compass point" on where you need to start looking to resolve the issue. Also the service monitoring, activity monitoring, and critical event thresholds really empower the teams to know when a problem is happening and they can get ahead of it before the first call even reaches the Help Desk. Nexthink is a cornerstone tool in our environment for end user experience and I'm excited to see where the go next.
Its great if you need real-time visibility across complex or regulated environments. Also strong for hybrid or multi-cloud setups where uptime, observability and fast IR are required. It’s probably overkill for smaller teams or environments that don’t have constant changes or compliance reporting needs. It's expensive and has a steep learning curve. Also, in my opinion, do not get yourself into a consumption based model. Costs can certainly get out of control quickly.
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.
The on-premise solution can be slow at times and resource-demanding even on newer laptops. (This isn't the case with the cloud offering.)
Some useful features are only available to cloud customers.
Library pack configuration could be made easier, often these packs require some customization and it's not always clear how to get them up and running after importing.
You can use table-like functionality to generate dashboards, but these queries are heavy on the system.
It could be easier to give insight into what type of line parsing is used for specific documents in a company-managed environment and/or show ways to gain the insights needed.
I would like to see ways to anonymize specific data for shared reports without pre-formatting this in a dashboard on which reports could be based.
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
When there is an issue, it’s a win if one can easily identify the root cause. To do the same, it should allow the user to dig deep with multiple data points and compare the data and identify the anomaly. In this use case, it’s good to drive from Splunk 011y.
Nexthink had better integration and a better user interface. 1E did not have the engagement capability which is so critical to many of the actions we complete using Nexthink. Nexthink had better trending data capabilities. 1E did not capture and hold data the way Nexthink does so all data assumes you are able to pull information from all systems at any time. with remote systems it is unlikely you will capture all systems at the same time so it makes any actions less effective. this review was performed 4 years ago so 1E may have addressed some of these limitations but Nexthink has also grown and continues to add and improve on their industry-leading capabilities.
Splunk Infrastructure Monitoring provides far superior options for anybody using a complex hybrid multi-cloud environment and allows both your SOC and NOC to work together on the same data while driving their own insights. We found other products are still in the old world view of servers and agents residing together within a single data centre, but modern apps are no longer like this.
SCCM proactive remediation: Automatically resolving hundreds of SCCM issues per month
Hardware: Identification of over $5m cost avoidance by seeing a lack of usage for 128GB SSDs - no need to upgrade to 256GB... coupled with OneDrive migration packs in the Nexthink library this is valuable.
