New features in Azure Monitor metrics explorer based on your feedback

A few months ago, we posted a survey to gather feedback on your experience with metrics in Azure Portal. Thank you for participation and providing valuable suggestions! We appreciate your input, whether you are working on a hobby project, in a governmental organization, or any size company—small to huge. We want to share some of the insights we gained from the survey and highlight some of the features that we delivered based on your feedback. These features include:Resource picker that supports multi-resource scoping.Splitting by dimension allows limiting the number of time series and specifying sort order.Charts can show large number of datapoints.Improved chart legends.Resource picker with multi-resource scopingOne of the key pieces of feedback we heard was about the resource picker panel. You said that being able to select only one resource at a time when choosing a scope is too limiting. Now you can select multiple resources across resources groups in a subscription.  Ability to limit the number of timeseries and change sort order when splitting by dimensionMany of you asked for ability to configure the sort order based on dimension values, and for control over the maximum number of timeseries shown on the chart. Those who asked, explained that for some metrics, such as “Available memory” and “Remaining disk space,” they want to see the timeseries with smallest values, while for other metrics, including “CPU Utilization” or “Count of Failures,” showing the timeseries with highest values make more sense. To make it possible, we expanded the dimension splitter selector with Sort order and Limit count inputs.  Charts that show large number of datapointsCharts with multiple timeseries over the long period, especially with short time grain are based on queries that return lots of datapoints. Unfortunately, processing too many datapoints may slow down chart interactions. To ensure the best performance, we used to apply a hard limit on the number of datapoints per chart, prompting users to lower the time range or to increase the time grain when the query returns too much data. Some of you found the old experience frustrating. You said that that occasionally you might want to plot charts with lots of datapoints, regardless of performance. Based on your suggestions, we changed the way we handle the limit. Instead of blocking chart rendering, we now display a message that suggests that the metrics query will return a lot of data, but letting your proceed anyways (with a friendly reminder that you might need to wait longer for the chart to display).   High-density charts from lots of datapoints can be useful to visualize the outliers, as shown in this example:   Improved chart legendA small but useful improvement was made based on your feedback that the chart legends often wouldn’t fit on the chart, making it hard to interpret the data. This was almost always happening with the charts pinned to dashboards and rendered in the tight space of dashboard tiles, or on screens that have smaller resolution. To solve the problem, we now let you scroll the legend until you find the data you need:  FeedbackLet us know how we’re doing and what more you’d like to see. Please stay tuned for more information on these and other new features in the coming months. We are continuously addressing pain points and making improvements based on your input.If you have any questions or comments before our next survey, please use the feedback button on the Metrics blade. Don’t feel shy about giving us a shout out if you like a new feature or are excited about the direction we’re headed. Smiles are just as important in influencing our plans as frowns!
Quelle: Azure

Why cloud-native development matters

Can we all agree that market research statistics should be taken with enough grains of salt to make your cardiologist worry? Good. Having said that, I’m now going to quote some market research statistics. But I do this not to focus on the numbers, but the fact that these numbers came from surveys and interviews of people just like you, and underline the trends and expectations that are driving the IT world today.
A rapid shift to cloud over the next three years will drive enterprises to move 75 percent of existing non-cloud apps to cloud environments. This research from IBV also found that in three years about 95 percent of internally developed apps are expected to be deployed on the cloud with 55 percent of newly developed apps designed as cloud-native. And, the most impressive stat I’ve heard recently is that from 2018 through 2023, million new logical apps will be created. This stat from IDC is equal to the number created over the last 40 years. These trends are contributing to the adoption of cloud-native development.
In the race to transform, enterprises embark upon their journey to cloud-native to deliver innovation at scale and at lower cost. Cloud-native applications do more than just run in the cloud; they’re designed and developed to maximize the economies of cloud. Cloud-native architectures and applications deliver faster time to market, higher scalability, in most cases superior customer experiences, simpler management, reduced cost through containerization and cloud standards, and more reliable systems without vendor lock-in.
Cloud native uses the strengths and accommodates the challenges of a standardized cloud environment. Adopting a cloud-native approach isn’t only about developing new generations of applications in better ways. It’s also about organizational culture. Enterprises must also transform to adopt a cloud environment successfully.
How and where to start the cloud-native journey
Containers and cloud-native applications have already been established and proven successful in large-scale cloud computing companies, but they are just expanding to enterprises. Enterprises are now beginning to learn the technologies and change how they approach development and operations. Enterprises are building applications within increasingly diverse IT environments. These range from traditional on-premises; to cloud native, which embraces containers and Kubernetes; to a hybrid, multicloud model. Most enterprises are in research and experimentation mode, with only a very small segment having experience or deployments of containers today.
The ability to innovate quickly while modernizing and using existing investments is key. The move to cloud native, along with the importance of maintaining current application performance levels, further highlights the pressing need to modernize operations and applications to move to cloud. To keep up with the competition, enterprises must regularly build new applications and update existing applications. To satisfy this demand, enterprises require an application platform that’s built on open source and open standards, that allows them to quickly build, test and deploy applications in a modern, microservices based architecture.
Three advantages of cloud-native development on IBM Cloud Pak for Applications
IBM Cloud Pak for Applications uses the power of open source technologies to help enterprises speed cloud-native application development and has some key advantages.
1. Broadest choice of industry runtimes
IBM Cloud Pak for Applications supports enterprise application needs through a choice of industry leading runtimes and choice of developer tools and modernization toolkits, DevOps and Apps/Ops Management.
2. Simplified build, deploy and management of applications
Enterprises can quickly build applications on any cloud, while providing the most straightforward path to modernize heritage applications. Kabanero.io, an open source project, which is an upstream for Cloud Pak for Applications, simplifies the build, deployment and management of applications. It offers an integrated experience from the creation of a cloud-native application on a developer’s laptop through testing and deployment in a container and on through the application’s ultimate managed lifecycle.
3. Modernization that maximizes existing investments
Enterprises can optimize their current investments, whether on-premises or in any public or private cloud. With IBM Cloud Pak for Applications, enterprises have the comfort of knowing they can modernize based on their unique timeline. They can realize ROI and are able to continue their cloud journey without ripping and replacing or getting locked in with a particular vendor. And when ready to modernize, enterprises can take advantage of a rich set of transformation tools including in the IBM Cloud Pak for Applications.
Ready to find out more?

Register to join our webinar 21 January 2020 at 9 AM ET.
Learn more about IBM Cloud Pak for Applications on our website.
Download the analyst report about the value of IBM and Red Hat.
Watch the replay of our version 4 release webinar.
Take a tour of IBM Cloud Pak for Applications.

 
The post Why cloud-native development matters appeared first on Cloud computing news.
Quelle: Thoughts on Cloud