Versions Compared

Old Version 17

changes.mady.by.user Daria Lebedeva

Saved on

compared with

New Version 18

changes.mady.by.user Daria Lebedeva

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Department, Team, Site, Project within your enterprise

  • Customers, if you're an MSP

  • Purchasers, if you're a reseller, etc

Creating an a Cloudaware application also makes sense in such cases when, for example, 1) there are AWS, Azure and Physical servers in your Cloudaware environment and you need to provide access to view AWS data only, or 2) only 1 AWS instance should be available for the application user, etc. Note that the sooner you create the application, the better since billing and cost data is not retrospective - it may be collected and shown in the app only starting the day when the application was created.

Table of Contents


Key Features

  • Multi-cloud and non-cloud support

  • Cascades give you ability to attach object hierarchies by attaching single object

  • Inventory automation using auto-attachment rules

  • Ability to attach objects that are not taggable or exceed the tag limit.

Prerequisites


Think of the assets that should be attached to the application you will be working on. You may create a list view showing running AWS instances, for example. Consider the logic that can be used for attaching assets in question to different tiers of the application.

Application Creation

1.  Log in to your Cloudaware account. Locate the section CLOUDAWARE in Navigator → Applications. 

...

You can continue OR if it is preferable, you can detach them clicking Detach Objects.

...

Cascades

Consistency is one of the main challenges you face when you try to be organized. Once of the best practices is to follow relationships between objects and use these relationships to get consistent and auto-updatable inventory.

...

  1. Try to minimize manual attachments. When you manually attach something, there is a logic for choosing an objects behind it. It's much better to implement that logic in an auto-attachment process, because Cloudaware will keep track of new objects that comply with your logic. If you need to attach something by hand, try to attach only truly static resources.

Auto-Attachment Processes


Cascades are good but they only work for big services with lots of interconnected objects. What would you do with all objects that have no relationships with each other? The answer is to implement the process that will monitor your assets and automatically validate them against defined rules and choose the application accordingly. These are auto-attachment rules.

...

The object will be automatically attached to an appropriate application within 1 hour.

Attachment Logic Examples

  • if Name starts with prod set Tier Name to "The Application - The Tier"

  • if tag:Customer equals CustomerA set Tier Name to "The Customer App - The Tier"

  • if tag:Application is not empty and tag:Tier is not empty set Tier Name to tag:Application+" - "+tag:Tier

...

You can create even more complicated auto-attachment rules combining workflow rules with formula fields or even updating them via API from external system. Almost any complicated object classification logic is possible using workflows and formulas.

Object Re-attachment After Application Tier Client Name Change

If Application Tier Client Name is changed, objects will be re-attached in 1 hour. However, there may be a delay in jobs if a customer didn't log in for some time.

...