15 ans à aider les entreprises françaises
à choisir le meilleur logiciel

Description de Splunk On-Call

Solution de suivi des problèmes qui alerte le personnel de garde et lui permet de travailler immédiatement sur le problème, même à partir d'un appareil mobile.

Qui utilise Splunk On-Call ?

Capacité à collaborer lors de la résolution d'incidents informatiques.

Splunk On-Call Logiciel - 1

Splunk On-Call ne vous convainc pas tout à fait ? Comparer avec une alternative populaire

Splunk On-Call

Splunk On-Call

4,5 (32)
10,00 $US
mois
Version gratuite
Version d'essai gratuite
21
21
4,3 (32)
4,6 (32)
4,5 (32)
VS.
À partir de
Types de licence
Fonctionnalités
Intégrations
Facilité d'utilisation
Rapport qualité-prix
Service client
79,00 $US
mois
Version gratuite
Version d'essai gratuite
124
19
4,4 (445)
4,5 (445)
4,5 (445)
Les jauges horizontales vertes représentent le logiciel le plus apprécié selon la note globale qui lui a été attribuée ainsi que le nombre d'avis.

Alternatives à Splunk On-Call

ManageEngine OpManager Plus
Fonctionnalités les mieux notées
Aucune fonctionnalité n'a été évaluée par les utilisateurs de ce logiciel.
SysAid
Fonctionnalités les mieux notées
Alertes et remontée des problèmes
Gestion des billets
Gestion des tickets de support
NinjaOne
Fonctionnalités les mieux notées
Accès et contrôle à distance
Alertes et remontée des problèmes
Gestion des correctifs
OpsGenie
Fonctionnalités les mieux notées
Alertes/Notifications
Notifications en temps réel
Planification des gardes
PagerDuty
Fonctionnalités les mieux notées
Gestion des incidents
Notifications en temps réel
Rapports d'incidents
Pulseway
Fonctionnalités les mieux notées
Accès et contrôle à distance
Accès mobile
Suivi des serveurs
Germain UX
Fonctionnalités les mieux notées
Alertes/Notifications
Mesure des performances
Rapports et analyses
Salesforce Service Cloud
Fonctionnalités les mieux notées
Base de données de contacts
Gestion des listes d'attente
Historique des clients
Splunk Enterprise
Fonctionnalités les mieux notées
Journaux des événements
Journaux du serveur
Monitoring

Avis sur Splunk On-Call

Note moyenne

Note globale
4,5
Facilité d'utilisation
4,3
Service client
4,5
Fonctionnalités
4,2
Rapport qualité-prix
4,6

Avis classés par taille de l'entreprise (nombre d'employés)

  • <50
  • 51-200
  • 201-1 000
  • >1 001

Trouver les avis classés par note

5
59%
4
34%
3
6%
Jeremy
Jeremy
Cloud Services Engineer, Operations
Utilisateur LinkedIn vérifié
Logiciels, 201–500 employés
Temps d'utilisation du logiciel : plus d'un an
Source de l'avis
Source : GetApp

The perfect fit

5,0 il y a 8 ans

Commentaires : When we went looking for an alerting solution, we wanted something that would make life easier for our folks on-call, as well as something that would help us clean up and make sense of the nigh-impassable flood of alert emails we were seeing constantly from our monitoring. Allowing folks to use their own devices also meant that there was no confusion as to how to reach out to someone, and it's something they always have on them. We were immediately captured by the Twitter-like timeline, so that every person (on-call or not) could view the incoming stream from the entire environment, and the rest of the features common in this space seemed very well-implemented. Since then, they've added tons of new features (the Transmogrifier and Control Calls each were game-changers) that have only made the service better. My director has identified this as the single best product we've implemented in the past two years, based on its impact to our team's efficiency and happiness.

Avantages :

- Communication-centric design - great for team efforts - Very responsive support and dev team - Easy to set up, easy to use - Lots of integrations available - Contact details in the app makes reaching out to teammates easier in a crisis

Inconvénients :

- Some advanced/niche scheduling options are not currently possible - Data on old alerts can be difficult or impossible to obtain, depending on age - Reporting is a work in progress

Réponse de l'équipe de Splunk

il y a 8 ans

It's wonderful affirmation for us when we hear that VictorOps has been a positive driver in team efficiency and happiness! We're also continuing to advance our development efforts (our engineering team is also growing!), so keep an eye out for enhancements on reporting and scheduling!

Utilisateur vérifié
Utilisateur LinkedIn vérifié
Biens de consommation, 5 001–10 000 employés
Temps d'utilisation du logiciel : 1 à 5 mois
Source de l'avis

Victory for on-call and alert escalation

4,0 il y a 4 ans

Commentaires : 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!

Avantages :

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.

Inconvénients :

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.

Justin
DevOps Engineer (É.-U.)
Logiciels, 201–500 employés
Temps d'utilisation du logiciel : plus de deux ans
Source de l'avis

Cheap, but that's about it

3,0 il y a 3 ans

Commentaires : IMO, Splunk bought VictorOps to tick a checkbox and nothing more. It's cheap, but unless you're totally strapped for cash, look elsewhere.

Avantages :

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.

Inconvénients :

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.

Utilisateur vérifié
Utilisateur LinkedIn vérifié
Internet, 201–500 employés
Temps d'utilisation du logiciel : 1 à 5 mois
Source de l'avis

VictorOps: Now Brought to You By Splunk

4,0 il y a 5 ans

Commentaires : Splunk's purchase of VictorOps gives the opportunity for major improvement and excellent customer support.

Avantages :

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.

Inconvénients :

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.

Michael
Michael
Ecommerce Specialist
Utilisateur LinkedIn vérifié
Vente au détail, 1 001–5 000 employés
Temps d'utilisation du logiciel : 6 à 12 mois
Source de l'avis
Source : GetApp

VictorOps

4,0 il y a 8 ans

Commentaires : 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.

Avantages :

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.

Inconvénients :

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.

Réponse de l'équipe de Splunk

il y a 8 ans

Thanks for such a positive review! We see people make the switch from PagerDuty on a regular basis, not just because of our feature set, but because we also put our users first. It's great that you noticed that too. It's also good to note that if you capture each incident as a post-mortem report, you'll always be able to go back and reference it. However if you need a more specific way to reference past incidents, I would definitely suggest you drop our support team a line. They are constantly looking for ways to improve the product, and would love to hear your ideas.