Virtual machine scale set insights from Azure Monitor

In October 2018 we announced the public preview of Azure Monitor for Virtual Machines (VMs). At that time, we included support for monitoring your virtual machine scale sets from the at scale view under Azure Monitor.

Today we are announcing the public preview of monitoring your Windows and Linux VM scale sets from within the scale set resource blade. This update includes several enhancements:

In-blade monitoring for your scale set with “Top N”, aggregate, and list views across the entire scale set.
Drill down experience to identify issues on a particular scale set instance.
Updated mapping UI to display the entire dependency diagram across your scale set while supporting drill down maps for a single instance.
UI based enablement of monitoring from the scale set resource blade.
Updated examples for enabling monitoring using Azure Resource Manager templates.
Use of policy to enable monitoring for your scale set.

Performance

The performance views are powered using log analytics queries, offering “Top N”, aggregate, and list views to quickly find outliers or issues in your scale set based on guest level metrics for CPU, available memory, bytes sent and received, and logical disk space used. 

These views will help you quickly determine if a particular instance is having an issue, and provide the means to troubleshoot the issue, specified down to the process that is having a failed connection to a backend service or a particular logical disk running out of space.

Maps

Our dependency maps and network connection data sets are powered by the service map solution and it's Azure Virtual Machine extension. Maps in this context deliver a view that is specific to your scale set, automatically discovering the processes on the instances that are accepting in bound connections and making out bound connections to backend servers. This allows you to identify surprise dependencies to third party services, monitor failed connections, see live connection counts, monitor bytes sent and received per process, and identify service level latency.

In addition to the map view, you can analyze the network connection data set in our connections overview workbook or directly in log analytics.

Workbooks

We have brought our workbooks from Azure Monitor for Virtual Machines to the scale set view. These workbooks query the monitoring data we collect and allow you to modify them to create custom reports that you can share with colleagues in the portal.

Getting started

If you’re running VM scale sets you can use the performance and map capabilities from the “Insights (preview)” menu on the scale set resource blade to find resource constraints and visualize dependencies.

To get started, go to the resource blade for your VM scale set and click on “Insights (preview)” in the monitoring section. When you click “Try now” you’ll be prompted to choose a log analytics workspace, or we can generate one for you. You can view your resources at scale in Azure Monitor under “Virtual Machines (preview)” and on-board to entire resource groups and subscriptions using Azure Policy or using Powershell.
Quelle: Azure

Instana Releases Red Hat OpenShift Kubernetes Operator Built on Quarkus

This is a guest post by Jon Skog, Senior Product Marketer at Instana Red Hat OpenShift introduced Kubernetes (K8s) Operator support with version 3.11. Since that time, the number of Operators created by the OpenShift community has been steadily growing. Instana introduced our Red Hat OpenShift Kubernetes Operator at Red Hat Summit 2019, and will […]
The post Instana Releases Red Hat OpenShift Kubernetes Operator Built on Quarkus appeared first on Red Hat OpenShift Blog.
Quelle: OpenShift

App Engine second generation runtimes now get double the memory; plus Go 1.12 and PHP 7.3 now generally available

Last year, we announced App Engine second generation runtimes, which let you use any language library, have direct network access, and connect to Google Cloud VPC Networks, giving you a more idiomatic developer experience, support for native modules and faster execution. Today, we are excited to announce that all App Engine second generation runtime instances will receive double the memory. In addition, Go 1.12 and PHP 7.3 runtimes for App Engine standard are now generally available.Doubling the RAM for all App Engine second generation applications lets them more easily  load language libraries or scale vertically to increase concurrency via multiprocessing or multithreading. This increased memory limit is already available for all apps running second generation runtimes; you don’t need to take any action to receive the additional memory. This upgrade comes at no additional cost.Please refer to the table below for more information on memory associated with each instance class.1: F4_1G and B4_1G have been renamed to F4_HIGHMEM & B4_HIGHMEM for accuracy. The original _1G instance names will continue to work and will receive 2,048 MB of memory.In the past year, we’ve announced a number of second generation runtimes, including Node.js 10, PHP 7.2, Python 3.7, and Ruby 2.5 (alpha). Today we are announcing the general availability of two new runtimes: Go 1.12 and PHP 7.3.A1 Comms is one of the UK’s leading mobile phone and telecommunication providers, and is using PHP to as it transforms its business from brick-and-mortar to online retail:“Moving to second generation runtimes has saved us a lot of debugging time and helped us increase performance by at least 50%. The PHP 7.3 runtime is giving our developers the best of the bleeding edge for Laravel compatibility and speed, while still providing automatic security patching to meet our compliance requirements. It exceeds our expectations for reliability. The inclusion of native support for the OpenCensus module for Stackdriver Trace is also something we are excited about. .” – Sam Melrose,  System Engineer, A1 CommsAdditionally, second generation runtimes are interoperable with our recently released Cloud Run, a serverless compute offering that allows you to run any stateless container in a fully managed fashion or on top of an existing GKE cluster. You can take apps that were built on App Engine second generation runtimes and move them to Cloud Run, or vice-versa.Forget infrastructure and focus on your usersWhile there are a lot of new things to love about second generation runtimes, the core value for App Engine remains: the service allows developers and companies to focus on creating great software while taking advantage of Google Cloud’s world class operations and infrastructure to scale, monitor, and manage their applications.“App Engine has literally been a game changer for us. Since migrating to it, I’ve yet to have a board meeting where we need to discuss availability or capacity or any other reason for downtime. In fact, during Black Friday while some competitors’ websites slowed or went down, our response time actually improved.”  – Jonathan Liversided,  IT Director, A1 CommsApp Engine Second Generation runtimes are available for use immediately, so start building your app today.
Quelle: Google Cloud Platform