If you are using InfluxDB to monitor your data and systems, then alerts may be an essential part of your workflow. We currently have a system for monitoring your data whether it enters a critical or non-critical state. Here I’m going to give a detailed guide on setting up alerts using our InfluxDB Cloud product as well as some best practices for having a good experience using alerts.
You may already be using Splunk to ingest data and generate alerts and dashboards so you can take quick action on problems, but did you know you can quickly start a VictorOps trial and in three easy steps, have great Splunk alerts escalated to the right teams and people with a mobile app notification, SMS message or a live phone call?
“The way we work has changed forever.” Those are words that our CEO Jennifer Tejada used in her interview with Yahoo Finance a couple of weeks ago. Those words made me stop and think about how much of our customers’ daily work has changed irreversibly. Working from home has changed from a luxury to a necessity, so how do folks in the IT world adapt to this change?
The IT landscape is constantly evolving. A tool that is heavily used this month, may be virtually obsolete the next. In a such a dynamic ecosystem, the methods used to implement these tools are unique to every organization. Therefore, it has become crucial for organizations to implement an incident response process that incorporates any combination of tools, even those that are highly siloed and departmental.
There’s no question that subscription-based businesses are an incredibly popular revenue model in today’s economy. While single transaction revenue models tend to fluctuate due to the seasonality of markets, subscription plans offer much more consistent and predictable revenues. Although the subscription revenue model can certainly be advantageous over one-off transactions, these businesses are also notoriously challenging to keep subscribers active on their plan.
