The Case: Maestro Brings a New Touch to Corporate Cloud Reporting



Effective cloud usage for an enterprise requires various tools, including resource management, corporate integrations, and establishing effective communication with end users.

By default, cloud providers offer crucial alerts out-of-the-box, with additional alerts being customizable and provisioned as a service. This setup works well once you use only one provider and a small infrastructure. However, in multi-cloud and hybrid cloud environments, tracking complex infrastructures efficiently becomes more challenging.

Enterprises have different methods to address these challenges, ranging from manual sorting to integrating third-party tools. However, not all these methods are flexible enough to respond promptly to technological updates and market demands. This is where the need for a better solution emerges, leading to our case study on migrating to Maestro.

Problem Statement

An enterprise using a hybrid cloud with AWS, Azure, GCP, and OpenStack-based infrastructure utilizes a legacy system for virtual resource management and user communication. The current system overwhelms users with excessive notifications, causing them to miss or ignore crucial alerts. Additionally, it provides insufficient details on reported findings and not enough analytics for the current scale of infrastructure, placing extra load on the support teams. 

The enterprise requires a new approach that enhances cloud analytics and reporting, making it more transparent, efficient, and valuable for both the enterprise and individual users within it.

Proposed Solution

The Maestro team offered connecting the enterprise infrastructure to an on-premises Maestro entity, focusing on customizing the reporting system to address the customer’s existing tasks and improving analytics, recommendations, and report usability. 

The team estimated the reporting system migration and customization would take 6 months and initiated the work.

Investigating the Legacy System and Updates Planning

At the start, the team analyzed the legacy reporting system and identified 130 reports sent to users. To facilitate working with the reports, we categorized them into five groups:


Understanding the target audience allowed us to revise the content of the reports, align them with those in Maestro, and determine updates to enhance the entire report collection's usability. 

As a result, we identified which information could be restructured, removed, or added. We also reassessed the recipients of each report to ensure they receive only pertinent information they can act upon. Additionally, we incorporated Maestro reports not available in the legacy system to provide deeper insights into FinOps and Security analytics and recommendations.

To the existing pack of the reports, we also added Maestro reports, that were not available in the legacy system and give deeper insights into FinOps and Security analytics and recommendations.

Migration Planning

In addition to sorting recipients and purposes, we categorized the reports to be migrated or added by their impact to construct a precise migration plan. This resulted in the following migration targets:



It was also agreed that the letters that are sent to the support teams would not be migrated to Maestro within the current scope, and would remain within the legacy system.

Pre-Migration Styling

One of the tasks within the migration was to ensure that each report in the resulting library had a recognizable style, was easy to read, and clear. All reports were to have a unified structure, color scheme, formatting, and consistent wording. 

To achieve this, we engaged a team of a designer, technical writer, and quality assurance experts to create a straightforward style guide. This guide provides clear instructions on all report parameters and is based on usability, readability, and common sense principles.


After the style guide was approved, the reports scheduled for migration were reviewed against this guide to ensure they met the criteria and aligned with the customer’s internal requirements.

How It is Going

The reporting system migration is currently underway, with Stage 2 nearing completion and over 100 reports finalized. We anticipate that the customer’s legacy system will be fully replaced by Maestro by the end of the year, with the first reports scheduled to run in production in October. 

We still face challenges, such as lacking Maestro equivalents for several reports or organizational constraints preventing migration. We continue to address these issues and will summarize the project results upon completion. 

Meanwhile, if you are new to Maestro or wish to refresh your knowledge about its detailed reporting and analytics systems, consider exploring the following articles:

Popular posts from this blog

Maestro Analytics: Essentials at the Fingertips

Image
Infrastructure analytics is one of the cornerstones for effective cloud management. Each cloud provider offers its own set of features and services for such purpose. We can say that AWS QuickSight, Google Data Studio, and Microsoft BI are among the top of the native analytics and BI offerings. They are deeply integrated into their native infrastructures, provide the detailed review of the infrastructure state, events and cost, and allow to take a deep dive into details, being powered by strong internal mechanisms and AI/ML engines. However, in many cases they provide a huge volume of data which needs a BI expert to cope with, as well as may have limited customization possibilities in terms of the covered data scope. Also, if you use more than one cloud, or have private datacenters, the fact that each of these tools is limited to its vendor, may be a reason for you to find a third-party analytics tool. Here is where you may consider solutions such as CloudHealth, AppOptics, or IBM C...
Read more

Maestro: Greeting the Green Dragon

Image
The year is coming to the end, and it's high time for our traditional lookback on Maestro evolution, changes, and important events. The year of 2023 has been dynamic and full of updates, both technical and strategic.  We kept to our previous commitments , meanwhile adjusting to the new trends in Cloud and technologies in general.  We met our user's expectation and need for  cross-cloud FinOps, automated infrastructure analytics, security assessment and the "Fix it" button , aimed to simplify issues remediation. We also took into account the rising demand for  Open Stack-based resources, Cloud Native approaches,  AI/ML integrations .  As a result, we came up with our standard "six release per year" cycle, highlighted with the following milestones: Maestro Insights With the ML technologies growth, the amount of services offering infrastructure recommendations and analytics, grow. This is true for the public cloud providers' native services, as well as thir...
Read more

Maestro Orchestrator: Product? SaaS? Framework!

Image
In 2012, EPAM Cloud Orchestrator was created as a cloud solution for the EPAM Systems community. It appeared when the issue of redesigning the growing infrastructure of more than 500 projects became critical. After a thorough analysis of the existing solutions, EPAM experts had to admit that none of them fit the company needs. However, that was not a problem but a challenge. If no perfect solution existed, EPAM created its own from scratch. In six years, EPAM Cloud Orchestrator evolved into a true hybrid cloud with over 8000 virtual machines in hundreds of projects. In addition to its basic function - hosting virtual resources - it supports a number of related components helping the users to be in full control of their virtual infrastructures, such as audit, monitoring, billing, reporting. Meanwhile, a time has come to go out of the box of an enterprise solution and meet the market. This is how the new generation of EPAM Cloud Orchestrator - Maestro was born. Maestro is ...
Read more