To find out more about cloud migrations, the pitfalls that await the unwary, and what the security implications are, I recently sat down with Dustin Dorsey, Systems & Data Architect at Biobot Analytics, based in Cambridge, MA. In the first post in this series, we talked about cloud providers being responsible for security ‘of’ the cloud, while their clients are responsible for security ‘in’ the cloud.

Elastic® SQL inputs (metricbeat module and input package) allows the user to execute SQL queries against many supported databases in a flexible way and ingest the resulting metrics to Elasticsearch®. This blog dives into the functionality of generic SQL and provides various use cases for advanced users to ingest custom metrics to Elastic®, for database observability. The blog also introduces the fetch from all database new capability, released in 8.10.

There’s only so much you can control when it comes to your app’s performance. But you control what is arguably most important - the code. Sentry Performance gets you the code-level insights you need to resolve performance bottlenecks.

While the cloud is recognized as more secure than on-premises servers and infrastructures, it does come with the often talked about shared responsibility model. Cloud providers are responsible for security ‘of’ the cloud, while their clients are responsible for security ‘in’ the cloud. It’s ‘differently secure’, rather than the traditionally secure organizations have been used to when working with on-premises environments.

Being able to execute SQL performance tuning is a vital skill for software teams that rely on relational databases. Vital isn’t the only adjective that we can apply to it, though. Rare also comes to mind, unfortunately. Many software professionals think that they can just leave all the RDBMS settings as they came by default. They’re wrong. Often, the default settings your RDBMS comes configured with are far from being the optimal ones.

Learn the best practices for executing seamless database schema migrations within ephemeral environments.

When the services in your distributed application interact with a database, you need telemetry that gives you end-to-end visibility into query performance to troubleshoot application issues. But often there are obstacles: application developers don’t have visibility into the database or its infrastructure, and database administrators (DBAs) can’t attribute the database load to specific services.