Sold by: ObserveAny
Focus on building apps and not managing Apache SkyWalking with a scalable, resilient and secure Observability platform. Observability with SkyWalking made simple on AWS.
4
Overview
What is ObserveAny? ObserveAny is a fully managed, truly cloud-native Apache SkyWalking service for integrating and processing all of your data in real-time, no matter where it lives. With ObserveAny fully managed cloud service on AWS, you can eliminate the burdens and risks of self-managing SkyWalking and focus more time on building apps that differentiate your business.
Pay as you go provides a no commitment, low friction way to quickly get started with ObserveAny by paying only for what you use.
To learn more about our cluster types, available features, and pricing, go to https://www.observeany.com/
Highlights
- Observable system based on Apache SkyWalking
- Quickly deploy modern monitoring and security in one powerful observability platform.
- Create actionable context to speed up, reduce costs, mitigate security threats and avoid downtime at any scale.
Details
Sold by
Categories
Delivery method
Deployed on AWS
New
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Buyer guide
Gain valuable insights from real users who purchased this product, powered by PeerSpot.
Financing for AWS Marketplace purchases
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Pricing
Pricing is based on actual usage, with charges varying according to how much you consume. Subscriptions have no end date and may be canceled any time.
Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator to estimate your infrastructure costs.
Dimension | Cost/unit |
|---|---|
ObserveAny Hosts per hour - 45 Day Retention | $2.03 |
Vendor refund policy
Pay As You Go
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA) .
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
Delivery details
Software as a Service (SaaS)
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
Resources
Vendor resources
Support
Vendor support
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Updated weekly
By ObserveAny
By Observe, Inc.
By Datadog
Top
25
In Issue & Bug Tracking
Top
10
In Application Performance and UX Monitoring
Top
100
In Log Analysis
Sentiment is AI generated from actual customer reviews on AWS and G2
Functionality
Ease of use
Customer service
Cost effectiveness
Positive reviews
Mixed reviews
Negative reviews
AI generated from product descriptions
Distributed Tracing and Monitoring
Observable system based on Apache SkyWalking for monitoring distributed applications and microservices
Cloud-Native Architecture
Fully managed, cloud-native service deployed on AWS eliminating self-management overhead
Real-Time Data Processing
Real-time integration and processing of observability data from multiple sources
Security Integration
Integrated security monitoring capabilities within the observability platform for threat mitigation
Scalable Infrastructure
Scalable and resilient infrastructure supporting observability operations at any scale
Data Ingestion and Query Performance
Ingests petabytes of telemetry per day with capability to process hundreds of terabytes and execute tens of millions of queries daily without performance degradation
Knowledge Graph Architecture
Utilizes O11y Knowledge Graph to structure and correlate data across logs, metrics, and traces for fast search and correlation capabilities
Natural Language Processing for Incident Analysis
Enables troubleshooting of complex incidents using natural language queries through O11y AI for accelerated root cause analysis
Open Data Lake Foundation
Built on Snowflake data lake architecture providing open data storage without vendor lock-in
Multi-Signal Correlation
Correlates and correlates telemetry signals across logs, metrics, and traces with context-aware analysis for incident resolution
Multi-Source Data Integration
Collects and correlates data from more than 600 vendor-backed technologies and APM libraries in a single platform
Unified Observability Dashboard
Provides full visibility into health and performance across all environment layers through a single pane of glass
Infrastructure and Application Monitoring
Monitors underlying infrastructure, supporting services, applications, and security data simultaneously within one observability platform
Rapid Deployment and Setup
Enables quick deployment through turn-key integrations and easy-to-install agent for monitoring servers and resources
Security and Performance Analytics
Delivers actionable insights to reduce costs, mitigate security threats, and prevent downtime across any scale
Standard contract
No
Customer reviews
Henry Mwawai
Monitoring cloud workloads has provided real-time insights and supports rapid root cause analysis
Reviewed on Jul 20, 2026
Review from a verified AWS customer
What is our primary use case?
I have been using Apache SkyWalking for three years to monitor systems, cloud-native applications, and my Kubernetes environment. With this, I am able to analyze and troubleshoot applications in real time without experiencing any lags.
I use Apache SkyWalking mostly for database monitoring, particularly for my MySQL database, where I am able to monitor response time and identify any latency or errors. Apache SkyWalking has enabled me to associate application logs to identify errors that have been helpful in my work.
When monitoring my MySQL database with Apache SkyWalking, I am able to report issues and get an overview of the multiple services running in my SQL. I receive alerts if there are any anomalies in my SQL, and Apache SkyWalking has been very useful in helping me troubleshoot my MySQL in real time without any challenges.
Another important aspect of my use case with Apache SkyWalking is its role in designing my Kubernetes monitoring to help me monitor pods, nodes, and the container workloads currently running. With this, I am able to know the performance metrics for the applications running in my Kubernetes.
What is most valuable?
In my opinion, the best features that Apache SkyWalking offers include service topology mapping where you can automatically discover service dependencies. Another valuable feature is application performance monitoring, where you can track response time in real time. Additionally, metrics collection allows you to collect metrics from databases, operating systems, and applications. Another useful feature is log correlation, which helps link logs and allows you to connect log entries for faster incident investigation.
Apache SkyWalking has impacted my organization positively by supporting integration with external systems in place in the environment. The log correlation feature has hastened incident investigation and helped connect requests with distributed traces. Multi-language agent support is a modern feature that makes Apache SkyWalking suitable for organizations using diverse technology stacks, such as Python, PHP, and Rust. Since it is open source, it is a fully useful tool. The fact that it supports Kubernetes and other cloud-native deployments has helped the organization remain secure from a security perspective. It has also helped scale large microservices environments since I can monitor different applications simultaneously using Apache SkyWalking, which has optimized application performance and boosted system health through increased visibility.
What needs improvement?
Regarding Apache SkyWalking's AI capabilities and governance and security, since Apache SkyWalking is an observability platform that contributes to operation security and monitoring for artificial intelligence systems through tracing, metrics, logging, and anomaly detection, I believe that from a governance perspective, it is not a dedicated AI governance solution. Organizations seeking comprehensive AI governance will typically pair Apache SkyWalking with governance processes and specialized tools that address model life cycle management, AI risk compliance, and responsible AI practices. For AI and compliance, I would rate it a two, but for operation monitoring and security, I would rate it a five.
Regarding Apache SkyWalking's AI capabilities in terms of accuracy and reliability outputs, Apache SkyWalking does not use AI algorithms to make predictions or decisions, so it does not have an algorithm accuracy matrix. It is an observability platform, not an AI model.
I rate Apache SkyWalking eight out of ten because it is a powerful open-source observability platform that is well-suited for organizations running microservices and cloud-native applications. However, the learning curve and deployment complexity may require experienced administrators, which prevents it from receiving a perfect score.
For how long have I used the solution?
I have been using Apache SkyWalking for three years.
What do I think about the stability of the solution?
Apache SkyWalking is stable in my experience.
What do I think about the scalability of the solution?
For Apache SkyWalking's scalability for my organization, I would rate it an eight. With that rating, we are able to accomplish a lot regarding the features in place, which has helped reduce significant time wastage in monitoring applications across the environment.
How are customer service and support?
The customer support for Apache SkyWalking is perfect.
Which solution did I use previously and why did I switch?
I have never switched to any other solution or used any other solution before Apache SkyWalking.
How was the initial setup?
Apache SkyWalking has been deployed using a typical cloud environment with agents installed in a cloud environment. For the back-end, I typically use Elasticsearch. For the agents, I have a cloud server being used. For the BTM analysis platform, I have a different server in the cloud that provides service topology and stores the processed data.
What was our ROI?
A relevant metric that we were able to capture is the time saved in associating multiple applications simultaneously to identify any downtime or errors. Since we are able to monitor applications at once in the same environment, significant money has been saved because we did not have to deploy multiple solutions for application reviews. Apache SkyWalking has enabled us to save considerable money in this regard.
Which other solutions did I evaluate?
I did not choose any other options apart from Apache SkyWalking.
What other advice do I have?
Apache SkyWalking is very useful and a nice application. I am able to perform root cause analysis, conduct monitoring, and have end-to-end visibility across distributed applications. There is also automated service discovery with the topology mapping. I believe Apache SkyWalking is on a safer side, and I do not have anything that I would need them to add or change. I am comfortable with what it offers right now. Apache SkyWalking is the best and will not fail you. Regarding cloud deployment, it is a very good application. I give Apache SkyWalking an overall rating of eight out of ten.
Saad Amin
Unified monitoring has streamlined trace analysis and now needs clearer setup and modern UI
Reviewed on Jul 06, 2026
Review provided by PeerSpot
What is our primary use case?
We have running Kubernetes clusters as well as the database and other servers with the main use case for Apache SkyWalking being the need for monitoring metrics and traces, and the slow endpoints of the applications, and the service-to-service communication chart and the graph of how the services are communicating with each other. Everything was under one umbrella of Apache SkyWalking .
We were facing a slow endpoint in our application, and this specific example of how I use Apache SkyWalking in my day-to-day work helped us there and also query some queries of the database which needed to be optimized. Apache SkyWalking helped us there.
I use OpenTelemetry to get the metrics out and the traces out of the application and the Kubernetes cluster and the servers, which is how I use Apache SkyWalking. I get that into Apache SkyWalking and its own good GUI. It is easy to integrate into the system. We have the Java applications, so it had also a dependency which we can add into the pom.xml of the Java application in the Spring Boot . This is the current situation where we used it and we got facilitated.
What is most valuable?
The communication from one service to other service with the best features Apache SkyWalking offers is the chart, the graph it displays, and the communication bubble which moves from one application to another, and also the name of the application and the connection to the database server. The whole chart explains the infrastructure very well to any other person. This is one of its beautiful GUI features. Additionally, we can get everything at one place. We don't need other tools such as ELK and other trace tools such as Zipkin or Jaeger. We just get everything in one single place.
These features have helped my team or made my work easier when we diagnosed our slow endpoints. Additionally, when we were going to deploy the new applications, we just had to confirm how it is communicating with other services and if it is able to make the connection to the database server. At that point, we were just being feasible while recognizing what the state of the application is. The alerting system for the machines, for the VPS, and for the Kubernetes cluster helps us in a lot of ways and in a lot of areas.
Apache SkyWalking has impacted my organization positively. We implemented it to diagnose the slow endpoints and we just started and integrated the other things, the DB, the Kubernetes clusters, the metrics, the logs, and the alerting systems. Apache SkyWalking helped us in every perspective.
Comparably, if we compare Grafana and Apache SkyWalking, they are both nearly equal in order to provide and send the alerts, which shows how Apache SkyWalking has benefited my organization. Apache SkyWalking made a difference that we can get everything at one place while with other tools, we have to deploy a single by single, one by one.
What needs improvement?
Features are good, but there is something about the UI, which I would suggest. There is space to enhance it and make it look less pointy from the edges and not like an old UI. There is a space where we can develop a more eye-catchy UI. Otherwise, it is all good.
Apache SkyWalking can be improved by addressing the UI, which is a thing that needs to be less complicated. A simple documentation on how to integrate it with Kubernetes and in the different Kubernetes clusters provided by different cloud providers such as GCP , OKE, the EKS, and even integrating Apache SkyWalking with Ranchers too would be beneficial. A good UI which should not be pointy and should be eye-catchy and acceptable would be beneficial.
For how long have I used the solution?
I have been using Apache SkyWalking since 2021 and in the start of 2022. This is the exact date I started working with Apache SkyWalking.
What do I think about the stability of the solution?
Apache SkyWalking will take time to get mature, which is my perspective on its stability. Right now, I don't think it is stable.
Which solution did I use previously and why did I switch?
Before Apache SkyWalking, I previously used ELK, Grafana , and Zipkin.
What's my experience with pricing, setup cost, and licensing?
It is fine regarding my experience with pricing, setup cost, and licensing.
Which other solutions did I evaluate?
There is nothing in terms of evaluating other options before choosing Apache SkyWalking.
What other advice do I have?
There are modifications which I already mentioned while explaining why I chose seven out of ten for Apache SkyWalking. These relate to AI, the deployment procedure, and the integrating procedure of Apache SkyWalking. There should be good documentation. The other thing is about the user interface.
I haven't experienced Apache SkyWalking's AI capabilities regarding its governance and security yet.
I haven't used Apache SkyWalking's AI capabilities regarding its accuracy and reliability of output.
Everything is good in terms of improvements needed for Apache SkyWalking that I haven't mentioned yet.
It depends upon their usage for others looking into using Apache SkyWalking. I won't recommend it to everyone if he or she is not operating a very big infrastructure. Then there is no need to use it. If someone is using a bigger infrastructure and wants everything in the right place and all in one place, then Apache SkyWalking would be ideal for that person. I rated Apache SkyWalking seven out of ten.
Rajeshk Kumar Nayak
Monitoring has improved and provides faster root cause analysis in complex microservices
Reviewed on May 30, 2026
Review from a verified AWS customer
What is our primary use case?
Apache SkyWalking is my primary tool for application performance monitoring and distributed tracing. On a daily basis, I use Apache SkyWalking to monitor application health and trace requests across microservices to identify performance bottlenecks, monitor response time, and troubleshoot application issues before they impact end users.
In an e-commerce deployment consisting of multiple microservices such as user management, product catalog, payment gateways, inventory, and order processing, Apache SkyWalking provides end-to-end request tracing. When a customer places an order, I can track the request as it travels through each service. If latency occurs in the payment services or inventory databases, Apache SkyWalking immediately identifies the affected component and helps us resolve issues much faster.
Apache SkyWalking provides visibility into complex distributed systems where traditional monitoring tools often struggle to pinpoint root causes.
What is most valuable?
Apache SkyWalking offers several best features including distributed tracing across microservices, real-time application performance monitoring, service topology visualizations, Kubernetes and cloud native integrations, and low monitoring overhead. The platform is open source and has a highly scalable architecture.
Service topology visualizations represent the most valuable feature. It provides complete visibility into how requests move between services, making troubleshooting significantly faster and reducing the time required to identify the root cause analysis and performance issues.
Apache SkyWalking has significantly improved application visibility and reduced troubleshooting times while enhancing security reliability. Operations teams can proactively detect issues before they affect customers, leading to better service quality and improved user experience. I have achieved approximately 50% reduction in troubleshooting time, a 30% improvement in incident resolution speed, faster root cause identification, and improved application uptimes. Additionally, reduced mean time to resolution (MTTR) represents specific outcomes and metrics I can share.
Apache SkyWalking provides strong observability and monitoring capability. From a governance and security perspective, it supports secure communications, role-based access controls (RBACs), and data collection controls. Organizations can implement security best practices to ensure compliance and meet governance requirements.
What needs improvement?
Areas for improvement include simplified initial deployment and configurations, better documentation for advanced use cases, and more built-in dashboards and reports.
A more user-friendly onboarding experience would help organizations adopt the platform more quickly, especially teams that are new to distributed tracing technology.
For how long have I used the solution?
I have been using Apache SkyWalking for the last two years.
What other advice do I have?
The tracing and tracing data generated by Apache SkyWalking is highly accurate and reliable when agents are properly configured. The platform will deliver its best results and consistently provides actionable insights that help operations teams make informed decisions.
Apache SkyWalking is deployed in a hybrid cloud environment across Kubernetes and OpenShift clusters, with the backend component providing scalability and high availability.
Apache SkyWalking is an open-source solution that I deploy directly using Kubernetes manifests, Helm charts, or in some environments, operator-based deployments.
If you have hosted microservice-based applications in any environment and want to track requests and transactions between microservices, Apache SkyWalking is an advanced monitoring tool that will help monitor microservice-based applications and check application health.
I would rate this product an 8 out of 10.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Aditya Bhatt
Monitoring has transformed issue resolution and now reveals full application and container health
Reviewed on May 14, 2026
Review from a verified AWS customer
What is our primary use case?
My main use case for Apache SkyWalking includes not only monitoring microservices and APIs but also managing the entire health of the application. I will explain the domains and backgrounds where we currently use it. It does more than check microservices or heavy queries. It can be integrated from the IT point of view, where your IT team can easily integrate it on the DevOps side or where applications are being deployed. It is widely used for managing the entire health of the application, checking the current status and health of the application, and how your services are currently running. When I mention services, this essentially means your queries, including database queries or backend logic that has been written to perform either up-syncing or down-syncing of data into the database or retrieving something, updating or inserting queries. Apart from that, it can be used for checking how your APIs are working, such as out of multiple API calls, how many are succeeding versus failing. If there is a particular timeout, I can see the frequency of recurrence and the time duration of the timeout or how long the network is unreachable.
Even in payment applications where we have multiple applications, some related to payment processing may be failing or insert queries may not be working. There could be multiple layers on the backend side of the architecture design, and during issue resolution, it is very difficult to analyze where the actual pain point area is. Apache SkyWalking really helps identify that a particular API call failed on the payment side, perhaps deep down three layers in the architecture design, so you can see that it is failing because of a specific reason, such as network timeout, unreachable network, the bank server being down, or a third party payment server integration not responding due to heavy traffic load.
In some other domains, beyond checking health, if your applications or servers are running on pods or Kubernetes containers, you can check the health of your pods as well. We have moved from outsystems to Mendix and other Java hosted applications and .NET, which all utilize Kubernetes and nodes. You can easily check which node is working fine and which is not in good state, how much traffic is currently passing through those containers or nodes, how they are integrated, and which one is responding fine versus not responding well enough. These are many areas where you can easily identify issues with the help of Apache SkyWalking. Because of its open use case platform, it helps from the licensing point of view and covers a wide area of use cases.
In terms of projects, I would like to share a couple of examples. One of our patient services applications was facing issues with API failures. It was initially identified that this might be because of Java database upgradation, the fact service getting down, or perhaps a global outage of some database server, so the entire API services was getting affected. Then some fact line services started getting impacted, and because of that, a few of our Mule APIs were not working fine. Since the project had the dependency of cross-functional team members, each team was trying to identify where the actual cause was lying. At a high level, we thought that the Java API might not be connecting properly with the fact API or the Mule API internally calling the fact API, which was not getting reached properly. Someone was trying to reach out to the Mendix team to see if they could figure out and find the logs, and it could be the .NET or other applications depending on what kind of application the team was currently working on. With the help of Apache SkyWalking, you can definitely have this in place and easily identify that for this particular time duration, this was the API call that went off and this was the feature that got stopped, and these are the documents that did not reach properly. You can easily identify the area and reach out to that team, stating that you need to check out these particular APIs, and you can reach out to the support team or the vendor if needed so that on the particular SLA, those can be taken care of on priority.
Apart from that, there is one more use case I would like to share regarding one of the applications on the local platform we built. Apache SkyWalking can be integrated there also because most of the time when a lot of traffic is coming for a particular second, there is sometimes a huge spike on Grafana or the logs and it is very hard to see that for a particular instant this much huge traffic is coming while your CPU or memory is quite low. You need to increase your space, but the logging is not able to maintain properly or pods are getting crashed and new pods are getting recreated. It is very hard to identify the logs to understand what is happening. Even in that area, you can easily integrate Apache SkyWalking and easily identify your Kubernetes containers and node health.
What is most valuable?
Apache SkyWalking offers the best features for integrating into the IT department to check microservices, the entire end-to-end health of the application, the node, Kubernetes, which queries are running fine, and which queries are running slow. From the SLA side, most queries should get completed within 200 milliseconds. If it is taking longer than that expected time, someone has to take the initiative to see where the room for improvement is.
I have been using Apache SkyWalking while encountering a couple of scenarios in the IT department along with a couple of projects we were working on. That is where I was doing some self-exploration to see how we can try to get through the bottlenecks of the root causes and how we can easily identify what the RCA is, why lots of microservices and APIs are getting failed, and what the bottleneck is. Because that project had a dependency of cross-team members, that is where I got to know about Apache SkyWalking and explored it. It is a really wonderful tool to go ahead with the IT team.
Apache SkyWalking helps me visualize data and performance by easily visualizing how the entire ecosystem is currently working. For example, if we have lots of Kubernetes containers in place and nodes being interconnected to multiple projects or products inside the organization, manually it is very hard to check out and take the export of the health of the containers and see how the traffic is going through which container is fine or bearing a lot of load and how we can shift it. Manually, it is going to take a lot of time. Visualizing it with the help of Apache SkyWalking is going to be a game-changer in such a way, reducing your time on that. You can easily visualize how the entire ecosystem is currently working. You can see where the current health is pretty much good and where the health of the system is degrading so that concern can be put into that sector as soon as possible.
Apache SkyWalking has positively impacted my organization by reducing the time of the team so that they can put in more efforts into their other tasks, saving a lot of time, improving our SLA in resolving any issue, providing good RCA analysis to the leadership team, and helping us in monitoring the entire health in a shorter time span.
What needs improvement?
Apache SkyWalking can be improved by enhancing a few things. The learning curve is definitely there, so it needs a good learning curve. Your engineers or experts need to be pretty much handy and sound on the technical side to use this platform. If it comes to customization, that is where it needs a deep understanding. The normal configuration you can easily do, but on the heavy customization side, it needs a good learning curve.
Secondly, on storage management, because you are doing the entire health checking and continuously monitoring the entire ecosystem, it occupies a lot of space. You need to either purge that storage and have something that can be recycled or put in some additional space in the archive section, and you can easily retrieve that after a certain period of time. If a million of records or traces are there, it becomes a heavy task. Storage management is something where it can be improved or explored much more to provide much more ease and convenience to the users who are opting for it.
Thirdly, some UI modifications can also be done to make it much more beautified. I would add that Apache SkyWalking should improve the storage complexity and how we can easily manage that, and some customization and heavy customization learning curve can be reduced. Making the UI much more convenient and much more beautified for the end user would be beneficial.
What do I think about the stability of the solution?
Apache SkyWalking performs well in terms of reliability and uptime. The only issue is with managing its storage complexity, which is the major one. Apart from that, it is pretty good.
What other advice do I have?
Apache SkyWalking integrates with other tools or platforms in my environment easily if you have a good learning curve on that and are able to understand the technicalities. The DevOps team will be able to do that easily.
Apache SkyWalking handles security and compliance requirements in my environment effectively, and I have found it helpful in identifying where the pain point area is while helping us in the RCA.
My advice for others looking into using Apache SkyWalking is that if someone is really interested in identifying the entire health of the application and how the ecosystem is currently working without giving load to the developers to write down any particular code to check health statuses, they can definitely go with Apache SkyWalking. That helps in identifying the entire thing for their application ecosystem, Kubernetes, cloud services, nodes, and monitoring their microservices call, the API calls, and current functioning. Deep down inside the architecture planning, it helps in identifying and monitoring and managing the entire application, helping you to reduce your SLA in solving out your issues, any kind of hot potato incidents or hot fixes or any impediments which the team is getting blocked with. That is where it helps a lot in identifying the area of improvement and also sharing the reports with the higher leadership team members. I would rate this solution an 8.5 out of 10.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Jaroslav Fikker
Monitoring has accelerated root cause analysis and provides clear dashboards over time
Reviewed on Feb 07, 2026
Review provided by PeerSpot
What is our primary use case?
Our main use case for Apache SkyWalking is for monitoring Java application servers such as Tomcat and WebSphere Liberty.
How has it helped my organization?
We have continuous information about the status of the application servers.
What is most valuable?
The best features that Apache SkyWalking offers are its user interface with graphical panels and charts. What I appreciate most about the user interface and panels is the ability to use different time periods in the chart and track resource consumption over time.
Using Apache SkyWalking has had a positive impact on my organization because it has enabled us to identify the causes of various problems more quickly. Identifying causes is now approximately five times faster than before.
What needs improvement?
Apache SkyWalking can be improved by responding more quickly to new versions of monitored products, including, for example, taking into account changes in Java class names.
For how long have I used the solution?
I have been using Apache SkyWalking for about two years.
What do I think about the stability of the solution?
Apache SkyWalking is stable in my experience.
What do I think about the scalability of the solution?
We haven't had any issues with Apache SkyWalking's scalability because we use it in a relatively small environment where we monitor dozens of servers.
How are customer service and support?
My experience with Apache SkyWalking customer support has been good. I have contacted the support community several times and the responses have been very quick.
Which solution did I use previously and why did I switch?
Before Apache SkyWalking, we used Broadcom CA Spectrum . We decided to switch from Broadcom CA Spectrum to Apache SkyWalking because of the license cost, as Apache SkyWalking is free.
How was the initial setup?
The initial installation of Apache SkyWalking went smoothly according to the available documentation.
What was our ROI?
I can't say how much ROI we've gotten from using Apache SkyWalking because I don't know the price of the original product (Broadcom CA Spectrum).
What's my experience with pricing, setup cost, and licensing?
Our experience with pricing, setup cost, and licensing for Apache SkyWalking is positive since it is free, which was the reason for our decision to use it.
Which other solutions did I evaluate?
We did not evaluate other options before choosing Apache SkyWalking.
What other advice do I have?
I recommend others looking into Apache SkyWalking to try it. I have given this review an overall rating of 8.