Sync upstream/integration (c317e0e) -> main 2025-11-21 #284
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* cloud adapter update * cloud adapter update * complete model * persistencia no clickhouse * feat(aws/s3): add IT status, sizes, access pattern; persist to MongoDB Extend S3 bucket metadata collection and persistence. - Compute total_size_bytes, object_count via CloudWatch (NumberOfObjects, BucketSizeBytes by StorageType) - Build tiers as [storage_class_name, size_gb] - Infer access_pattern (frequent/infrequent/mixed/unknown) from AllRequests; fallback to LastModified sampling - Determine it_status_bucket (enabled when IT applies to whole bucket) - Capture last_checked (ISO dates with non-zero requests) - Persist new fields in BucketResource (total_size_bytes, object_count, access_pattern, it_status_bucket, tiers, last_checked) * determine access pattern based on cost-generating requests * determine object counter * refactor(aws/s3): remove access_pattern - Remove access_pattern field and calculation logic - Keep only last_checked for GET request dates * feat: adding v0 implementation of the recomendation code for the Intelligent Tiering feature * feat/fix: add S3 Intelligent-Tiering module to frontend and fix returns * fix: name of new recommendation (S3 Intelligent Tiering) * fix: matching types on what is used and what it receives on te recomendation module * fix: creating aux function to parse types between the mongoDB and recomendation function * fix: return format of the intelligent-tiering recomendaton module * feat: adding access pattern as a factor on the formule to recomment IT to a bucket * fix: changing the saving cost formula to include access_pattern of the bucket * fix: adding back lifecycle and average size of objects per bucket to the recomendation formula * last check update to 90 days * last check update to 90 days * fix(frontend/service): add saving column and fix resource id * fix: removing avg object size from recomendation formula * fix: change resource_id return * fix(frontend): fix column savings * fix(frontend): fix description of Intelligent Tiering and remove pool column * docs: adding in-code documentation to the intelligent tiering recomendation * fix: Improving code readability to match review done by @annabeatrizlucena * fix: adding constants.py to the recomendation module * docs: document IntelligentTiering.tsx file purpose and structure * fix: improvements requested by reviewing and deleting files uploaded by mistake * refactor: comentar métodos relacionados a LogGroupResource * chore: remove commented-out methods related to LogGroupResource in AWS cloud adapter * chore: remove history file from PR * chore: remove history file from PR * fix: precommit linter checks * test pull request * archive for s3 it recommendation * fix linter errors * fix linter errors * remove comment block from IntelligentTiering.tsx Removed the comment block describing the IntelligentTiering class. --------- Co-authored-by: Geraldo Sobreira Junior <geraldo.sobreira.junior@ccc.ufcg.edu.br> Co-authored-by: anavirginianery <ana.virginia.souza.nery@ccc.ufcg.edu.br> Co-authored-by: andreza-vilar <andreza.farias@ccc.ufcg.edu.br>
## Description Formated some meta titles in resources table ## Related issue number https://datatrendstech.atlassian.net/browse/OSN-1155
- Updated TrafficMapMarker to use MUI Box for layout and added width/height props - Improved class handling with cx - Removed unused styles - Split "External and other clouds" destination to "External" and "Other" - Updated tooltip in TrafficExpensesMap to display detailed flow expenses and usage - Refactored the getMarkers function in useTrafficExpenses to accumulate locations and flows - Improved selection state management for rows and columns in the useTrafficExpenses hook
917d08c OSN-1177. Fixed not showing support_email text in some emails
- do not retry auth-reladed errors in CAd
- fixed retrying logic forced wrapper
ffaraone
approved these changes
Nov 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR syncs the latest changes from upstream to main.