Introduction: What’s New?
Hi there enthusiast! We are excited to bring the latest updates in Octo this week. This release brings you updates packed with enhancements and new features to make your cloud management experience even more efficient.
Dive into the details below ⬇️.
🆕Unit Cost (Alpha Version)
We are introducing a new feature in our Cost Group creation process. This feature serves as the basis for determining the cost of a specific unit of an item or entity within your business or organization. In this Alpha version, users can distribute costs among their unit items manually by setting percentages. Please note that this feature is still under development and subject to further improvement.
🆕Enhanced Insight Reports with ‘Usage Optimization’ and ‘Unrealized Savings’
This added section of your ‘Insights Reports’ focuses on recommendations related to usage optimization. It provides a summary of your unrealized savings. The section highlights which account could have had the highest savings (in addition to the savings you've already achieved through the executed recommendations) and identifies the recommendation that could have provided the most significant savings.
Unrealized Savings: Refers to savings that you could have achieved if only the recommendation were implemented.
You can see this section right after you create a new Insight Report.
🆕Four New Recommendations Added
Managing your cloud resources efficiently is the key to keeping costs under control and ensuring optimal performance. This week, we’ve added four new recommendations to help you get the most out of your AWS resources and keep those costs in check.
EC2: Reserved Instance Lease Expiration
Comprehend: Deletion of Underutilized Endpoints
Redshift: Deletion of Underutilized Clusters
Lambda: Excessive Time-Outs
For detailed information on each of these recommendations, please refer to documentation.
🆕Group By Tags
This newly added category in the group by feature in your cost group called ‘Tags’ aims to help you track your cloud spending specifically on projects, environment, etc. Each tag key corresponds to a tag value. When you click on a specific tag key, for example ‘env’, the data (tag value) are grouped under that specific tag key. Tag values that are not under any tag key are considered ‘untagged’.
Note: This supports only AWS and GCP vendors for now, with plans to include Azure in the future.
Minor Bug Fixes and Improvements
We have also made some minor bug fixes and improvements to other existing features.
We will continue to improve features based on user feedback.