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.
$15
per month (billed annually) per host
Tanzu tc Server
Score 6.1 out of 10
N/A
The Tanzu tc Server is a Lightweight Java application server that extends Apache Tomcat for use in large-scale mission-critical environments.
WebSphere Application Server is propriety and increases project cost. It is slightly complicated to learn when compared to Jboss EAP. These were the two main reasons why we chose Red Hat JBoss EAP over Websphere Application Server. Also, JBoss EAP is light weight and requires …
We decided to use Red Hat JBoss EAP as it lowers our overall cost, supports all the features that we are looking for including clustering, distributed caching and web services. JBoss EAP is modular and has cloud-ready architecture.
JBoss does practically everything Apache Tomcat and Weblogic does in terms of our requirements, but JBoss is more suited for larger enterprise J2EE apps compared to Tomcat. Boot time is not as quick as Tomcat, but still relatively fast for our deployments. The system can also …
Jboss supports JEE standards and provides features like high availability, clustering, hot deployments, configurable features. you can quickly add or remove needed features and cut jboss footprint and reduce boot time.
it could stack up against this version of Splunk because in this instance of having the cloud option as an available use case it furthermore has more use cases and the options for the data to always be readily available will furthermore allows for analysts to review the data in …
Datadog pushes intom proprietary ecosystem and pricing structure.Compared to self hosted prometheus and grafarna but it gave headache og managing our own monitoring infrastructure at scale.Prometheus is excellent for scraping cluster metrics but it doesnt handle distributed …
I guess scale is the main factor against grafana and ease of use against amazon elasticsearch service and also i have used signoz and ELK Stack also, but stability Splunk Observability Cloud gives is too good and also it comes with high avability and you have to maintain …
We initially chose Splunk Observability Cloud because it promised full-stack visibility and tighter integration. The other tools didn't offer this as part of the core package. Their analytics and real-time dashboards looked strong during the demo but it turned out to a lot …
I selected Splunk Observability Cloud because it focused so much on OTEL standards which will help us in future as OTEL is covering most of the observability standards. And also it has the best Kubernetes observability as I already explained it has several predefined dashboards …
Splunk Observability Cloud stood out for its real-time data ingestion, native OpenTelemetry support, and seamless correlation between metrics, traces, and logs, which gave us faster root cause analysis and better end-to-end visibility compared to Grafana setups that required …
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.
It's able to quickly detect and resolve issues across the entire spectrum of deployments including on-premises, public cloud, private cloud, hybrid cloud and multicloud
The above applications have their own use cases. Thousand Eyes or Sitescope is used for URL monitoring and Splunk is used for application monitoring. Appdynamics is also used for application monitoring and can monitor the server very well but it lacks when searching in logs …
Splunk is superior in many ways to these solutions when I'm comes to ingesting, storing, manipulating, and using data, but dynatraces automatic agents do make it much easier to use out of the box. Nagios seems much cheaper but does not provide as much functionality as Splunk. …
SQL is a great tool for smaller quick checks. When trying to monitor several different environments, applications, APIs, several thousand devices, connections, and technology, it just doesn't stand up to what you need. Splunk Infrastructure Monitoring has really stood out …
We are having other monitoring tools like AppDynamics, Dynatrace, Datadog and already using their end-user monitoring capability. Most of our customers are looking for agent-free monitoring where they don't want to instrument any agent on their client-side (as it might …
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 …
We selected Pivotal tc Server opposed to Cent0s Linux because Pivotal tc Server is more reliable and causes less downtime , also better logging. I have used both
It's well-suited for being less bulky and is more manageable than other IBM products for Java applications. It's more scalable and provides broader features than others, and is able to load balance with better visibility. The "containers" within are lighter weight and thus don't consume as many resources as Websphere did.
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.
-Pivotal tc Server is best used as web application server on a virtual machine for middleware purposes -I feel it is less appropriate to be used with utilizing data that does not need to be secure
JBoss deployment and configuration is easy and fast. This leads to lower cost and faster deliveries.
Jboss gives you lot of flexibility around performance tuning options to better suite your application needs.
It is modular and cloud ready. This can be installed on-premise and cloud with equal ease.
I specifically love it's integration with mod_cluster. It is a smart httpd based load balancing component that listens to incoming requests on web server using httpd and then intelligently routes the request to Jboss hosts.
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.
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
User management and administration access account setup has room for improvement and can be more user friendly and clearly list how many admin accounts we can setup
password complexity for user accounts need to be updated
although all logs list all errors some of the tomcat errors are not time stamped
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
It's quite easy to learn and use. We have transitioned our Red Hat JBoss EAP set up to client team. They had no technical background of managing it but were quick to learn the product.
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.
WebSphere Application Server is propriety and increases project cost. It is slightly complicated to learn when compared to Jboss EAP. These were the two main reasons why we chose Red Hat JBoss EAP over WebSphere Application Server. Also, JBoss EAP is light weight and requires less server resource
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.
We selected Pivotal tc Server opposed to Cent0s Linux because Pivotal tc Server is more reliable and causes less downtime , also better logging. I have used both