• Operate

Operational success is the achievement of outcomes measured by the defined metrics. Understanding the operational health of workloads, and knowing when operational events impact it, allows users to respond accordingly. To operate successfully, consider the health of cloud workloads and responses to issues.

Understanding Operational Health

The engineering team needs to be able to easily understand the operational health of cloud workloads. Use metrics based on operational outcomes to gain useful insights. Then use these metrics to implement dashboards with business and technical viewpoints that help team members make informed decisions.

Devek makes it easier to bring together the best monitoring and analytics cloud services, and use those to analyze cloud workload and operations logs, revealing the operating status of systems, and affording insight from operations over time. Collect log data from workloads and systems and send it to a log aggregation service, then define baseline metrics to establish standard operating patterns. Use monitoring visibility and observability systems to present system and business level views of these stored metrics using a central dashboard.

One example for this is using Elsatic Metricbeat and Filebeat to send metrics to a service providing Elasticsearch, and then use Kibana to create dashboards and visualizations of the operational health like order rates, connected users and transaction timing. Devek brings out of the box templated dashboards that provide alerts and remediation guidance when systems are experiencing events that might affect the business.

Responding to Events

Anticipate planned operational events such as sales promotions, deployments, and failure tests, and unplanned events such as surges in utilization and component failures. Use existing runbooks and playbooks to deliver consistent results when responding to alerts. Defined alerts need to be owned by a role or a team that is accountable for the response and escalations. Use dashboards to reveal any business impact of system components’ behavior and use this to target efforts when needed. Perform a root cause analysis (RCA) after events, and then prevent recurrence of failures, or document workarounds.

Devek simplifies event response by providing tools supporting many aspects of workload monitoring and visualization. Improve recovery time using Devek by replacing failed components with known good versions very quickly, rather than trying to repair them. Then carry out an analysis of the failed resource, possibly in an alternate environment provisioned using Devek.

Devek supports numerous tools provided by third-parties that allow for monitoring, notifications and responses. Some of these tools are New Relic, Splunk, Loggly, SumoLogic, Datadot, ElasticSearch, Pagerduty, and more. Know when a human decision is needed before taking action. When possible, have that decision made before the action is required. Keep critical manual procedures available for use when automated procedures fail.

Join Devek in reducing Cloud complexity

Looking to reduce complexity of cloud infrastructure? Look no further, we are here to make it happen!
Please leave some details and we will get back to you when Devek is available for trying out.

we only use this e-mail for the release announcement

or e-mail us at contact@devek.cloud
Devek will become available in the following months.