Frequently asked questions

For further inquiries, reach us on [email protected]

General

    2. Most of the definitions of an incident are - an event that could lead to loss of, or disruption to, an organization's operations, services or functions. Not all incidents affect your customers and most of these incidents come to light. With Spike, we help with the right alerting to bring these incidents to you.

    3. Consider Spike as a central place for absolutely any and all of your incidents. We alert the right person at the right time with the right incident to help them resolve it.

    4. Almost instantly (yes, almost!). In order to start receiving incidents, you will need to add integrations; follow the guidelines on the docs.

    5. A general rule of thumb we recommend is - Ask yourself (or your team) on every module they created, what could go wrong? How do they get to know about it?. We currently seamlessly integrate with a few integrations and we are adding more each week. You can choose to either use these integrations or use our webhook integration and start receiving incidents from all your monitoring tools.

    6. We recommend a few monitoring tools we love like AWS, GCP, Healthchecks, Rollbar, Sentry etc. to keep a tab on every single service/module etc you build.
    Here's one quick example:
    1.  Healthchecks.io for monitoring your cron jobs
    2.  Apex Ping or Uptime Robot for uptime monitoring
    3.  AWS or GCP, etc for your all of your managed services on the cloud
    4.  New Relic for Application monitoring
    5.  Using RabbitMQ, Sidekiq, Kafka etc.? Use our webhook and receive incident alerts
    6.  DB backup failed? Setup our webhook and receive alerts
    Above is a good starting point.
    General rule of thumb is you should monitor everything that could possibly go wrong for each feature you release.

    7. This is completely normal. We can help you with onboarding and setup of your entire account over a call that suits your timings. We don't do a weekly demo that you have to enroll and wait. Email us at [email protected] and we will set you up. And NO, we don't charge for helping you through the setup. We charge for delivering value not find excuses to charge you as and when possible

Alerts and Incidents

    2. We believe incidents affect businesses of all sizes and everyone should have access to Spike to receive alerts and take actions to resolve incidents. We never want to not alert you of an incident because of capping the number of alerts. Worry about your incidents, not the alerting costs.

    3. We use top of the line vendors to give alert you via email and phone call. We also alert you via Slack.

    4. Sharing the responsibility of managing incidents is very important. If you are a team and manage multiple services then add your team, share the load and collaborate on incident resolution.

    5. We take your integration requests and build it within our 72 hours. Email us at [email protected]

Subscription and Cancellation

    2. If an incident occurs after the trial, you won't get any alerts regarding it. You will get timely notifications about upgrading your accounts.

    3. You can cancel your subscription by visiting the Billing section and clicking the cancel button. We never ask you to contact our support team or dial a number to cancel your subscription. You don't want it then we get it. No hard feelings.

    4. You can still access the entire dashboard and data. No data is deleted from our databases unless you want us to. For data deletion from your account, email us at [email protected] and we will help you out.

    5. You can add as many team members as you like. There is no limit to it. We calculate your monthly subscription cost based on the maximum team members that are part of your account for each month. If you remove someone then rest assured it will be reflected in your billing.

Have more questions? Reach out to us via live chat or email us at [email protected]