Resource Usage Analytics - configure the scoring logic

Now that you have created a resources usage analysis and start looking at the results, one of the main parameters is how the different resources are rated: the scoring logic of the component.

See the current scoring logic for a cost partition or cost partition unit

You have access to the scoring logic by clicking the "cog" button next to the name of the current scoring logic:

You can change the scoring logic for the entire cost partition (first screenshot below where the cost partition has a generic scoring logic) or for a particular cost allocation unit, in the second screenshot the "prod-no-sla" cost allocation unit has no scoring logic.

List of the built-in scoring logics

When you click the button "change scoring logic" (1) you will see a list of preconfigured scoring logics for some typical component of a cloud architecture:

  • Generic Server Scoring Logic
  • Batch Worker Node Scoring Logic
  • Web Frontend Scoring Logic
  • Web Backend Scoring Logic
  • List Unattached EBS Scoring Logic
  • Web Frontend With ResourceGroup Awareness Scoring Logic

For each you have different parameters (CPU, Network, memory, etc. ) for which you can change the weight in the scoring by clicking the "edit" (2) button. You can also choose to disable the scoring logic for a particular cost allocation unit by clicking the "disable scoring" button (3)

After you have made your edits, click on the "apply" and "recompute scores" (4) to update the analysis results.

When you edit a scoring logic (2), you will be able to change the different weights of a metrics in the scoring logic:

Use a personalized scoring logic

You can also create a custom scoring logic either:

  • by choosing the "Generic Server Scoring Logic (configurable)" under the "Custom Scoring Logics Templates" section (1)
  • by starting from scratch with specific metrics (2)

In the first case when you edit the scoring logic you will have access to all the metrics and their respective weights:

While for the second option you can fine-tune the scoring logic even further by editing the configuration manually based on JSON. For more information please contact our support team at

Export and Import your scoring logic templates with the Teevity CLI

To download and learn more about how to use the Teevity CLI and API please refer to this page.

If you want to manage your scoring logic templates via the CLI, here are the commands to use:

  • teevity rua describe-componentLevelScoringLogicTemplate <componentLevelScoringLogicTemplateUUID> which returns the full JSON description with default parameters values
  • teevity rua create-componentLevelScoringLogicTemplate --name "<scoringLogicTemplateName>" --definition-file "<scoringLogicDefinitionFilePath>" to create a new scoring logic template
  • teevity rua update-componentLevelScoringLogicTemplate --scoringLogicTemplateId <scoringLogicTemplateUUID> --name "<scoringLogicTemplateName>" --definition-file "<scoringLogicDefinitionFilePath>"