fix: set Monitor Retention Policy#167
Closed
infracost[bot] wants to merge 1 commit intomasterfrom
Closed
Conversation
This commit was automatically generated by Infracost Autofix
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
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
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.
💰 Infracost opened this pull request as part of the following campaign:
Manual Optimization Campaign
Policy: Monitor - consider using a retention policy to reduce storage costs
Use a retention policy to avoid retaining analytics data indefinitely and accumulating storage costs. For example, if an application generates 5GB of logs daily, in a year without retention, you'd store 1.8TB of logs. In the Azure East US region, data retention costs $0.10 per GB per month after the first month. This means you'll incur an additional yearly cost of around $1,000 compared to a service that has a simple 30 day retention policy.Risk: Medium
improper retention could prematurely delete logs still needed for compliance or debugging.Deployment details: No downtime expected, Please see Azure docs for details
retention policies apply in‑place to Log Analytics workspaces without service disruption.Next steps:
✅ Deploy this change before the campaign deadline: March 21, 2026
💬 False positive? Add a PR comment with
@infracost dismiss🛠️ Incorrect code fix? Close the PR with a comment or check out the branch to adjust