Operations | Monitoring | ITSM | DevOps | Cloud

In the last few years, the usage of databases that charge by request, query, or insert—rather than by provisioned compute infrastructure (e.g., CPU, RAM, etc.)—has grown significantly. They’re popular for a lot of the same reasons that serverless compute functions are, as the cost will scale with your usage. No one is using your site? No problem: you’re not charged.

In today’s article, I will be highlighting eG Enterprise’s monitoring capabilities for Amazon’s AWS NICE DCV VDI protocol that was used first in Amazon’s AppStream 2.0 and now subsequently also in WSP 2.0 for the Amazon WorkSpaces service for digital workspaces.

If you’re embarking on a new project and evaluating public clouds, the cost involved will be one of your main considerations. You might decide to use Google Cloud Platform (GCP) as your primary cloud platform. If so, you’ll want to estimate costs based on listed prices. But it might surprise you to find a higher bill than you originally expected.

Setting FinOps KPIs helps keep your whole organization aligned toward the same financial goals. However, it takes more than simply setting a broad, company-wide financial goal and turning every employee loose to work on that goal without more specific directions. It’s far better to come up with realistic and achievable goals tailored toward each person or team that will be responsible for them. That’s because KPIs should ideally be focused around the typical persona of each team.

With serverless and containerized applications becoming a norm, workloads and integrations are spread across multiple cloud environments. As these apps become increasingly more distributed, monitoring also becomes more complicated with siloed and incomplete telemetry. This is where distributed tracing brings great value. It enables end-to-end visibility in your modern and complex application.