✨ Optimize Log Analytics Costs

Open
#4,187 2 comments 0 reactions 0 assignees View on GitHub

A pull request for this has already been merged.

  • #4488 by @copilot-swe-agent — merged

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure, nextjs
Domain
cloud, observability-sre

Research direction

Start with the Azure Portal Log Analytics usage-and-costs view linked in the issue, focusing on app requests and app dependencies. Analyze the current ingestion, identify an optimization, and verify that reduced ingestion does not negatively affect website performance or functionality.

Written by the indexing model from the issue text.

Description

Needs Refinement YakShaver

Requested by: @chrisschultzssw via YakShaver.ai 🦬
cc: @chrisschultzssw, @brookjeynes-ssw, @adamcogan, @babakamyljanovssw

Hi Team!

  🟥  Watch the video (37 sec)

  Url from screen share: https://portal.azure.com/#@sswcom.onmicrosoft.com/resource/subscriptions/b8b18dcf-d83b-47e2-9886-00e2983e29e9/resourceGroups/sswcom.au/providers/Microsoft.OperationsManagement/solutions/log-sswwebsite-9eb3/usageAndCosts

Pain

The current log analytics costs for the SSW Website are estimated to be $55 per month, which seems high. The goal is to reduce the amount of data ingested for app requests and app dependencies to lower costs.

Acceptance Criteria
  1. Analyze current log analytics data usage for app requests and app dependencies.
  2. Identify potential areas for optimization to reduce data ingestion.
  3. Implement changes to reduce log analytics costs.
  4. Verify that the changes do not negatively impact website performance or functionality.
Screenshot

Screenshot
Figure: High log analytics cost due to 19GB app requests and 9GB dependencies

Dominant language
HTML
Stars
14
Forks
10
Avg merge
13h 51m
Merged PRs (30d)
38

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SSWConsulting/SSW.Website

All issues in SSWConsulting/SSW.Website

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.