

PagerDuty Operations Cloud and VictoriaMetrics operate in the IT operations management domain. PagerDuty has an advantage in incident response optimization, while VictoriaMetrics excels in scalable monitoring and data visualization due to its robust feature set.
Features: PagerDuty Operations Cloud provides incident management, real-time alerts, and automation tools. VictoriaMetrics offers high-performance analytics, scalable data storage, and a powerful query language.
Ease of Deployment and Customer Service: PagerDuty Operations Cloud integrates seamlessly with existing systems, reducing downtime during deployment and receives positive reviews for its responsive customer service. VictoriaMetrics, although requiring more setup time for complex configurations, benefits from detailed self-service documentation and strong community support.
Pricing and ROI: PagerDuty Operations Cloud has a higher initial setup cost but offers a favorable return through enhanced operational efficiency. VictoriaMetrics provides strong ROI due to low-cost entry and high data processing capabilities, making it attractive for budget-conscious buyers seeking extensive data analytics.
The escalation was not possible at all before, which led to the L1 team being under too much stress.
The alert reduction feature has greatly impacted our ability to prevent costly incidents, as we can accurately respond to alerts with the help of autonomous AI agents, which reduces erroneous notifications.
We definitely save time with PagerDuty Operations Cloud. It saves more than half an hour—30 minutes—for each incident.
I have seen a return on investment with VictoriaMetrics, saving 40% in storage costs compared to Prometheus, reducing query latency by 60%, and cutting maintenance time by half.
time was saved due to simplicity and a shorter learning curve compared to other tools.
Because VictoriaMetrics runs more efficiently and much faster, debugging an issue or understanding system performance is much easier.
PagerDuty Operations Cloud is a good product for the organization and the support team is highly effective and responsive.
We have standing weekly calls to discuss any doubts, and there is a dedicated team, including an engineer and a PagerDuty Relations Manager, assigned to support us.
we have never had an issue when reaching out to someone in customer service
We reached out once or twice for minor issues during the initial setup and integration, and they were helpful in resolving the issues.
VictoriaMetrics customer support is exceptional.
We use the open-source version of VictoriaMetrics, so we did not require any customer support.
Scalability for PagerDuty Operations Cloud is excellent, and I rate it at 9.9.
Whatever top-notch tools we are using as an enterprise solution, PagerDuty Operations Cloud has kept itself current and integrates nicely with all the tools we use these days.
We are able to extend our PagerDuty Operations Cloud configuration without major challenges or changes to our overall operational model.
It handles large volumes of time series data efficiently, using less memory and disk compared to Prometheus or Thanos.
We deploy and embed it in our Helm chart and it works out of the box.
VictoriaMetrics has handled increases in data and users smoothly so far.
We have never experienced any downtime or latency issues from PagerDuty Operations Cloud.
It never breaks down for us, and considering I have devoted 20 years of my career to IT infrastructure operations, where everything typically breaks down, including Jira and ServiceNow, it is impressive to say that PagerDuty Operations Cloud has not caused disruptions.
PagerDuty Operations Cloud is the most stable solution.
In terms of accuracy and reliability, VictoriaMetrics's output is pretty sufficient and works very well in a native Kubernetes setup, which I appreciate.
The components are simple, restarts are fast, and stateless parts can be replaced without data loss.
Regarding stability, I would rate it a ten out of ten.
With many new members, they need training to set up runbook workflows, event orchestration, and manage complex on-call schedules across 23 services, making it a challenge for new users.
Additionally, I think a sandbox mode would be helpful for new team members, allowing us to guide them in simulating alerts, performing escalation policies, and creating PagerDuty Operations Cloud channels.
Additionally, if we could integrate an AI chatbot feature, such as asking who is on call and having it display the results, it would be beneficial because we have multiple teams and currently need to navigate different dashboards.
For our use cases, it is a really good offering, and while we would be interested to see what else it brings in the future, at this point in time it checks all our boxes and we are quite satisfied with it.
VictoriaMetrics is quite a good project and quite easy to use overall.
I compared it with my experience on other time series databases, and it has a huge advantage, so I do not see the need for urgent improvements or optimizations.
I had around seven users part of it for a base pricing of around $450 per user, primarily for custom workflows and the ITSM part.
The pricing for PagerDuty Operations Cloud is a bit expensive, especially for startups like us, compared to the other platform which I mentioned, which is Rootly.
Licensing is straightforward but scaling seats for larger teams can get expensive, especially when adding advanced features.
We did not require any license for VictoriaMetrics since we are using the open-source version.
I used the free open-source version, and it was sufficient for my needs.
My experience with pricing, setup cost, and licensing for VictoriaMetrics is positive since it is open-source under Apache 2.0, so there is no licensing cost.
In addition to those features, I also find the integration and reporting aspects of PagerDuty Operations Cloud valuable, as it records all triggered calls and incidents, enabling us to analyze patterns and identify the times when systems go down, thus assisting us in understanding and addressing the underlying causes.
Before, setting up everything was very difficult. Now, we don't have to think about it. We can simply set it up in PagerDuty and it works.
Scheduling with PagerDuty Operations Cloud has reduced confusion because we set it up with a round-robin rotation, and nobody needs to update it every day unlike with Excel, where we had to create a new schedule every two months.
The best aspect of using VictoriaMetrics is the reduction in resources including RAM, memory, disk, and other infrastructure requirements, which have all decreased substantially after implementation.
In my experience, the best features VictoriaMetrics offers include that VM agent does its work very efficiently and does not use a lot of resources.
Its compact storage and fast query performance make it ideal for long-term metric storage.
| Product | Mindshare (%) |
|---|---|
| PagerDuty Operations Cloud | 2.3% |
| VictoriaMetrics | 0.5% |
| Other | 97.2% |
| Company Size | Count |
|---|---|
| Small Business | 32 |
| Midsize Enterprise | 28 |
| Large Enterprise | 81 |
| Company Size | Count |
|---|---|
| Small Business | 3 |
| Midsize Enterprise | 2 |
| Large Enterprise | 2 |
PagerDuty Operations Cloud focuses on efficient incident management, featuring advanced alert and notification systems, mobile alerts, and AI-driven functionalities that facilitate streamlined on-call schedules and integrations with major monitoring tools.
PagerDuty Operations Cloud offers comprehensive incident management with real-time alerts and notifications via mobile, SMS, and calls. This empowers teams to respond swiftly and reduce missed incidents. Efficient on-call management through automated scheduling and escalation enhances team productivity, while AI-driven alert grouping minimizes noise. Integration with tools like AWS and Datadog further streamlines operations.
What are the key features of PagerDuty Operations Cloud?PagerDuty Operations Cloud implementation spans industries like e-commerce and IT services, where it automates anomaly detection and manages high-severity incidents. Its integration capabilities and AIOps features significantly enhance incident management, proving valuable for sectors demanding real-time performance and responsiveness.
Teams that switch to VictoriaMetrics report 70% less RAM and 75% less disk (verified PeerSpot user reviews), and cloud bills up to 10x lower (Grammarly case study) — while keeping their existing dashboards and alerting rules working. It is an open source observability solution for metrics, logs, and traces: a drop-in replacement for Prometheus and other backends that keeps scaling when data volume, query speed, or cost no longer does. It runs anywhere — from a Raspberry Pi to thousand-core clusters, on-premises or in the cloud — and is Kubernetes- and OpenTelemetry-compatible. Built by engineers, for engineers: Over 1B Docker pulls, 19M GitHub downloads, and 27K+ GitHub stars. Simple, reliable, and efficient observability for everyone.
VictoriaMetrics delivers observability in two complementary forms. The open source products are complete, production-grade, and free to run at any scale. Enterprise builds on that same code with capabilities and support for the most demanding environments — it extends open source rather than gating it.
Open source. VictoriaMetrics is a high-performance time series database and monitoring solution, compatible with PromQL via MetricsQL, so existing Prometheus dashboards, recording rules, and alerting rules keep working. VictoriaLogs is a logs database for mission-critical logging, and VictoriaTraces stores and queries distributed tracing data. All three are engineered for minimal RAM, disk, and compute at high ingestion rates.
Enterprise. VictoriaMetrics Enterprise adds features for large, multi-team deployments — plus direct support from the engineers who build the product, with architectural and security guidance. VictoriaMetrics Cloud is the same solution fully managed, and VictoriaMetrics Anomaly Detection applies machine learning to cut alert noise, so the alerts that do reach your team in Slack or on their phones are the ones that matter.
Measured results from users. PeerSpot reviewers report roughly 70% lower RAM use, 75% lower disk use, 3x faster writes, and 7x faster p95 query latency after replacing Prometheus. Grammarly cut its monitoring-related AWS bill about 10x; Granulate reduced metrics storage costs about 5x after moving from Grafana Cloud (Mimir).
Why teams choose VictoriaMetric
What are the key features of VictoriaMetrics?
What benefits and ROI should users expect?
Top use cases
VictoriaMetrics runs in production across finance, telecommunications, energy, scientific research, and IoT — from CERN's particle physics experiments to IHI Terrasun's utility-scale battery storage to Grammarly's product infrastructure. Wherever real-time telemetry at scale is critical, it delivers simple, reliable, and efficient observability for everyone. By engineers, for engineers.
We monitor all AIOps reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.