Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Set tags on your cloud resources at the infrastructure level #148

Open
wants to merge 2 commits into
base: dev
Choose a base branch
from
Open

Set tags on your cloud resources at the infrastructure level #148

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
77057d3
Create tag-resources.md
yelghali Oct 28, 2022
0882dbb
Update tag-resources.md
yelghali Oct 31, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 34 additions & 0 deletions docs/catalog/cloud/tag-resources.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,34 @@
---
version: 1.0
submitted_by: yelghali
published_date: tbd
category: cloud
tags:
- operations
yelghali marked this conversation as resolved.
Show resolved Hide resolved
dubrie marked this conversation as resolved.
Show resolved Hide resolved
- compute
- kubernetes
- role:software-engineer
- size:small
---

# Tag resources

## Description
Getting the right information and insights at the right time is important for producing reports about performance and resource utilization.

## Solution
Set tags on your cloud resources at the infrastructure level, to enable monitoring of your applications overall performance.


## SCI Impact
yelghali marked this conversation as resolved.
Show resolved Hide resolved
`SCI = (E * I) + M per R`
[Software Carbon Intensity Spec](https://grnsft.org/sci)

Regarding the SCI equation, tagging resource does not impact carbon emissions directly ; however it is a best practice that enables measurements and improvements.


## Assumptions
Naming conventions, and tagging governance is implemented.

## Considerations
Leverage Automation and infrastructure as code to help you implement an efficient and consistent tagging policy.