Add support for sub categorizations of ServiceCategory

[udam-f2]

Maintainer: Udam

Type

Dimension Normalized? Yes

Description

Today, ServiceCategory is defined as the highest-level categorization based on the primary function of the service. However, many find that the highest level of categorization can be too high-level and needs the next-level breakdown. A good example would be the Database ServiceCategory - which naturally has many well-known sub-categories such as Data Warehouses, Relational DB, and No-SQL (not an exhaustive list).

The request here is to add the subcategorization for ServiceCategory as a fast-follow for v1.0.

related issue from AWS-ZachErdman: https://github.com/FinOps-Open-Cost-and-Usage-Spec/FOCUS_Spec/issues/379

[udam-f2]

Related to #379 and #321

[thecloudman]

I've been reviewing this in my data and the need for sub categorisation is very much needed but we need to consider other columns in this decision so as not to duplicate data.

In Azure billing data we have meter category, meter subcategory and meter name, these are extremely useful in viewing usage across your azure spend. With FOCUS, these roll up, we have service category, service name and resource type, which means we lose a lot of good data we previously had.

Azure example in FOCUS format

Azure example in original format

The original format is far cleaner and easier to view and use. In FOCUS format we lose some of the detail behind the meters.

My view is we add additional columns which could be:

• SKU Description - can replicate meter name column from original data, as each meter has a unique SkuID.
• Resource Sub Type - which can be the same function as the Meter Category column in the original data.

I know this only focuses on Azure, but I believe it is fairly straight forwards to map google and AWS to this format.

[jpradocueva]

Classified as Service Category by the Maintainers on the May 24 call

[jpradocueva]

• [ ] TF1- #404 : Defining and Documenting Principles: Eric and Tim review the current Categorization principles, evaluate and document the principles for service categorization and subcategorization. Also, will ensure that any new subcategories fit within the existing structure without causing breaking changes.

Next Steps: Volunteers will start compiling and analyzing existing categorization data. The principles for subcategorization will be drafted and reviewed in subsequent meetings. Any necessary changes to the current categories and the addition of new subcategories will be planned for future releases beyond 1.1 to avoid breaking changes.

[jpradocueva]

Action Items agreed during TF-1 on Jul 9 call:

• [x] TF1-#404 Shawn: Prepare and present a draft of subcategories.
• [x] TF1-#404 Tim: Coordinate with Shawn for feedback on the draft.
• [x] TF1-#404 All Members: Review the draft when presented and provide feedback
• [x] TF1-#404 Irena will provide example hierarchies
• [x] TF1-#404 Shawn: Set up a meeting and include the Udam as Maintainer responsible for this item.

Documents

Folder: #404-subcategories Presentation: Service Subcategories Spreadsheet: Service Subcategories

Action Items

This was agreed during the TF-1 meeting on July 16:

• [ ] TF1-#404 Shawn: To lead the subgroup discussion in the “# tf-service-categorization” Slack channel and report back next week.

Action Items

Suggested during the Maintainer's call on July 22:

• [ ] Maintainers-#404 Irina and Shawn will prepare the initial proposal and facilitate discussions by August 12 to achieve TF consensus.

Action Items, TF-1, Jul 23:

• [ ] TF1-#404 Shawn: Update the draft to reflect the agreed-upon changes. Create a vote in the Slack channel for final decisions on open questions. Schedule a follow-up meeting to continue discussions and finalize subcategories.
• [ ] Team: Review and engage with the proposed changes and open questions in the Slack channel. Participate in the vote to finalize the categories and subcategories.
• [ ] Follow-up Meeting: A second meeting is to be scheduled for further discussions and to address any remaining open questions.

Action Items raised at the Member's meeting on Jul 25 call:

• [ ] Members-Shwan-#404: Finalize the subcategorization document based on feedback and continue the discussion on Slack.

Action Items from Task Force 1, call on July 30.

• [ ] TF1-#404 Chris: Draft a proposal for a potential "accelerated computing" subcategory under "Compute Virtual Machines."
• [ ] All Members: Review the current placement of monitoring solutions and provide feedback if further granularity is needed.
• [ ] TF1-#404 John: Compile a list of services and subcategories that could fall under a potential observability category for further discussion.

Action Items from the Maintainers meeting on Aug 5th:

• [ ] [Shawn-#404] Plan and document the sub-categorization structure for the Service Category.
• [ ] [TF1-#404]Develop a detailed proposal and implementation plan for review in upcoming meetings.

Action Items from TF-1 call on Aug 6th:

• [ ] [TF1-#404] Shawn: Issue a PR to adjust subcategories within the current set of categories.
• [ ] [TF1-#404] Shawn: Conduct further user group consultation to validate proposed changes and gather broader feedback.
• [ ] [TF1-#404] All Members: Review the principles guiding category changes to ensure they align with current needs and potential future adjustments.

  Action Items from TF-1 meeting on Aug 13:

• [ ] [TF1-#404] Shawn to issue a poll regarding the naming of uncategorized sub-categories.
• [ ] [TF1-#404] Shawn to proceed with creating a pull request for further discussions on category compositions.
• [ ] [TF1-#404] Riley to continue exploring whether identity should eventually be sub-categorized under security or remain as is.
• [ ] [TF1-#404] Chris to review the integration of streaming and API management services within the sub-categorization structure.

  Action Items, Members' call on Aug 15:

• [ ] [Members-#404] Shawn to create a PR, including descriptions, and share for further discussion.