--- description: Splunk On-Callを実際に使用したユーザーのレビューから、製品の機能や価格、メリットデメリットをご覧いただけます。類似製品との比較も簡単、ぴったりのSaaSが見つかるはず！ image: https://gdm-localsites-assets-gfprod.imgix.net/images/capterra/og_logo-e5a8c001ed0bd1bb922639230fcea71a.png?auto=format%2Cenhance%2Ccompress title: Splunk On-Callとは？ | 機能や料金、導入事例をご紹介【キャプテラ】 --- 現在地表示: [ホーム](/) > [インシデント管理ツール](/directory/31332/incident-management/software) > [Splunk On-Call](/software/139957/victorops) # Splunk On-Call Canonical: https://www.capterra.jp/software/139957/victorops ページ：1 / 3\ 次へ: [次ページ](https://www.capterra.jp/software/139957/victorops?page=2) > インシデント管理ソフトウェアがログ管理ツール、モニタリング・ツール、チャット・ツールなどに基づき、システムの健全性に関する統合ビューを提供します。 > > 評価：32人のユーザーによる評価は**4.5/5**。**おすすめ度**で最高の評価。 ----- ## 概要 ### Splunk On-Callの対象ユーザー インシデント対応スケジュールを調整し、インシデント対応チームに対象となるアラートを送信し、インシデントを解決するためのユーザー間のコミュニケーションをサポートする製品を必要とするDevOpsチームに主にサービスを提供します。 ## 簡単な統計と評価 | 測定基準 | 評価 | 詳細 | | **総合評価** | **4.5/5** | 32 レビュー | | 使いやすさ | 4.3/5 | レビュー全体に基づく | | カスタマー・サポート | 4.5/5 | レビュー全体に基づく | | 価格の妥当性 | 4.6/5 | レビュー全体に基づく | | 機能 | 4.2/5 | レビュー全体に基づく | | おすすめ率 | 80% | (8/10 おすすめ度) | ## 企業情報 - **キャプテラについて**: Splunk - **ロケーション**: San Francisco, アメリカ - **設立**: 2012 ## ビジネスコンテキスト - **価格プラン**: $10.00 - **価格モデル**: (無料のトライアル) - **対象となる企業**: 2～10, 11～50, 51～200, 201～500, 501～1,000, 1,001～5,000, 5,001～10,000, 10,000+ - **デプロイとプラットフォーム**: クラウド、SaaS、ウェブベース, iPhone（モバイル）, iPad（モバイル） - **サポートされる言語**: 英語 - **利用可能な国**: アメリカ合衆国, イギリス, インド, オーストラリア, カナダ, ドイツ, ブラジル, メキシコ, 中国, 日本 ## 機能 - Alerts/Escalation - Third-Party Integrations - アクティビティ・ダッシュボード - アップタイムレポート - インシデント・レポート - インシデント管理 - パフォーマンス・モニタリング - レポート／分析 - 監査証跡 ## 統合 (合計16件) - AppDynamics - Datadog - Google Voice - Jira - LogicMonitor - Nagios XI - Network Performance Monitor - New Relic - Pingdom - Raygun - Salesforce Sales Cloud - ServiceNow - Site24x7 - Slack - Sumo Logic ... さらに1件の統合 ## サポートのオプション - メール/ヘルプデスク - ナレッジベース - 電話サポート - 24時間対応（オペレータ） - チャット対応有 ## Category - [インシデント管理ツール](https://www.capterra.jp/directory/31332/incident-management/software) ## 関連カテゴリー - [インシデント管理ツール](https://www.capterra.jp/directory/31332/incident-management/software) - [サーバー監視ツール](https://www.capterra.jp/directory/32713/server-monitoring/software) - [APMツール](https://www.capterra.jp/directory/30208/application-performance-management-software/software) - [データセンター管理ツール](https://www.capterra.jp/directory/10054/data-center-management/software) - [サーバ管理ツール](https://www.capterra.jp/directory/10019/server-management/software) ## 代替製品 1. [Atera](https://www.capterra.jp/software/144309/atera) — 4.5/5 (446 reviews) 2. [PagerDuty](https://www.capterra.jp/software/125693/pagerduty) — 4.6/5 (219 reviews) 3. [Pulseway](https://www.capterra.jp/software/141792/pulseway) — 4.7/5 (310 reviews) 4. [SysAid](https://www.capterra.jp/software/107225/sysaid) — 4.5/5 (511 reviews) 5. [PRTG](https://www.capterra.jp/software/21581/prtg-network-monitor) — 4.6/5 (254 reviews) ## レビュー ### "VictorOps" — 4.0/5 > **Michael** | *2016年3月11日* | 小売 > > **良いポイント**: The transmogrifier has been an extremely useful tool for many of our teams. We've added playbook annotations to most of our alerts which has been a boon for our 24 by 7 support team. The Datadog integration has also shown VictorOps's savviness and people-centric approach to building a product. A Datadog VictorOps incident will send all of the pertinent information and graphs to an on-call users phone. The VictorOps mobile app can also be used as a platform to seamlessly chat with other users. We've also been encouraged by some of VictorOp's new features they have started to roll out. Their Statuspage.io integration has made many in our organization excited about the ability to have a one-stop-shop dashboard to communicate down-time incidents to a diverse group of users within our company. Their brand-new Control Calling feature (a feature that creates a conference call and pages users to join, penned "the new bat signal" by VictorOps) is also an intriguing feature that several of our teams have started to explore. Possibly our favorite aspect of working with VictorOps over PagerDuty is how responsive their team has been to both our support and development requests. > > **改善点**: VictorOps is still lacking some of PagerDuty's clerical and reporting functionality; for example, we no longer have the ability to easily reference a specific incident in the past. > > Prior to Bluestem Technologies migration to VictorOps, only a few of our squads were using Pagerduty for on-call incident management. Our major goals and justifications for switching to VictorOps was onboarding our entire technology team onto one on-call solution as well increasing our major incident responsiveness. VictorOps was chosen over PagerDuty for it’s people-centric focus, feature capabilities and cost. ----- ### "A really good product supported by a great team" — 4.0/5 > **Abdullah** | *2020年10月28日* | 小売 | おすすめ評価：7.0/10 > > **良いポイント**: - Easy to use and setup - Alerting data can be customized (found this feature missing on other competing software) - Ack-back feature (used Zabbix) - Very good mobile app with notifications - Alert snooze option which is a life saver. - Alert routing works perfectly > > **改善点**: - Duplicate alerts happen when alerts flap. - Alerting data contains too much data (relevant information is usually found after scrolling) > > VictorOps was the default on-call software for a couple of years for various teams in the organization. It works amazingly most of the time. Only issue that was faced was after Zabbix changed their alerting mechanism which somewhat broke the VictorOps. VictorOps team was quick to devise a solution using webhooks, which worked immediately. They however, took some time to figure out the ack-back solution for Zabbix 4.4, and had a bug which delayed the deployment. However, VictorOps support was really good throughout this time, they stayed in contact, and even let developers do live debugging to figure out the bug, and the solution was solved. All in all, I have nice things to say about VictorOps. ----- ### "Cheap, but that's about it" — 3.0/5 > **Justin** | *2021年5月10日* | コンピュータ・ソフトウェア | おすすめ評価：2.0/10 > > **良いポイント**: VictorOps (now called Splunk On-Call) organizes incidents in a manner similar to a Twitter timeline. It's really convenient being able to browse your history like that. There are a decent number of integrations with third-party services, and the Rule Engine allows you to annotate incoming alerts with additional information such as links to runbooks. In terms of price, you'll pay a lot less than you will for competing products like PagerDuty. > > **改善点**: Since being acquired by Splunk, VictorOps has been left to rot on the vine. There have been virtually no new features. I was willing to excuse that when VictorOps was operating as a smaller company, but not being able to do an in-depth history of incidents in 2021 is just inexcusable. Splunk's high-pressure sales agents will constantly try to upsell you on other Splunk products. SSO integration is still awkward to set up and use, and there still aren't nearly as many integrations as with PagerDuty. > > IMO, Splunk bought VictorOps to tick a checkbox and nothing more. It's cheap, but unless you're totally strapped for cash, look elsewhere. ----- ### "Victory for on-call and alert escalation" — 4.0/5 > **認証済みレビュアー** | *2020年9月23日* | 消費財 | おすすめ評価：8.0/10 > > **良いポイント**: VictorOps was easy to deploy, configure teams, and manage on-call rotations. There is a large list of integrations that allow for connections into all our required systems. Included with every integration is a link to their knowledge base. VictorOps is a must have tool for anyone looking to more effectively manage alert escalation and on-call rotations. > > **改善点**: There are only two things i have come across that are lacking. First, setting up overrides for on call management. VictorOps only allows for overrides to be in 30 minutes time blocks. This has caused issues with emergency on call coverage. Second is no having a location, out side the alerts and incidents, to house knowledge base type documents. > > For years we have had to manually manage our on call rotations throughout the organization. This linked with the wide range of monitoring tools, problem management has been difficult. VictorOps has allowed us to jump into the future of Outage Management\! This has allowed us to reduce our MTTR (mean time to resolution) for outages. I highly recommend this tool\! ----- ### "VictorOps: Now Brought to You By Splunk" — 4.0/5 > **認証済みレビュアー** | *2019年11月26日* | インターネット | おすすめ評価：10.0/10 > > **良いポイント**: Provides all of the necessary functionality for managing multiple teams of on-call professionals across an organization. App and Slack integration provide a feature-rich experience. override existing schedules, acknowledge or snooze alerts, see detailed history, and run reports. > > **改善点**: Some features are buried in menus, and the calendar is a little hard to use at times. Some options require clicking a specific toggle icon instead of just the text. > > Splunk's purchase of VictorOps gives the opportunity for major improvement and excellent customer support. ----- ページ：1 / 3\ 次へ: [次ページ](https://www.capterra.jp/software/139957/victorops?page=2) ## リンク - [Capterraで表示する](https://www.capterra.jp/software/139957/victorops) ## このページは以下の言語で利用できます | ロケール | URL | | de | | | de-AT | | | de-CH | | | en | | | en-AE | | | en-AU | | | en-CA | | | en-GB | | | en-IE | | | en-IL | | | en-IN | | | en-NZ | | | en-SG | | | en-ZA | | | es | | | es-AR | | | es-CL | | | es-CO | | | es-CR | | | es-DO | | | es-EC | | | es-MX | | | es-PA | | | es-PE | | | fr | | | fr-BE | | | fr-CA | | | fr-LU | | | it | | | ja | | | nl | | | nl-BE | | | pt | | | pt-PT | | ----- ## 構造化データ