Operations | Monitoring | ITSM | DevOps | Cloud

How can you judge Grafana vs. Chronograf and InfluxDB? Monitoring various systems is a crucial component of continuous maintenance. You can look at different parameters of the monitored system and take corresponding actions for certain conditions. For example, engineers can prevent server failure when they see the load on the server approaching its critical point. If the numbers of processed transactions (or registered users) exceed the expected level, you can celebrate your success.

A well-designed cloud architecture is essential to ensure that the underlying infrastructure stays operational, within budget, and compliant over time. These days, organizations are rapidly spreading their infrastructure across a broad, complex mesh of interconnected resources and services. It can be difficult to make high-level decisions about the design and management of these systems. This is why many organizations are now turning to cloud infrastructure modeling tools.

s3gw is an S3-compatible service, focused on deployments in a Kubernetes environment backed by any PVC, including Longhorn (https://longhorn.io). Since its inception, the primary focus has been on Cloud Native deployments, however, the s3gw can be deployed in a myriad of scenarios, provided there is some form of storage attached.

Critics of open source software have long argued that giving everyone access to a project’s source code creates security issues. But in active projects with highly engaged communities, the opposite is actually true: Open source software helps organizations become more secure. That said, any piece of technology can be exploited.

Moogsoft pioneered AIOps, essentially inventing the market 10 years ago. It is worthwhile revisiting why we did that to understand where we are going. My background is as the founder and inventor of Micromuse Netcool, and the RiverSoft’s OpenRiver technology.

As a cloud product manager, much of our jobs center around creating KPIs (or OKRs, if you prefer) such as sales revenue, freemium conversions, or customer stickiness, and encouraging development teams to hit product performance goals. But what happens after those goals have been met? Do we create new KPIs and push forward, or do we take a step back and evaluate whether each indicator actually translates to higher profit for the business?