Skip to content

Conversation

@shashax42
Copy link

Summary

Request to add a comprehensive monitoring and logging solution example for Microsoft Fabric resources to enhance operational visibility and alerting capabilities.

Motivation

Currently, the quickstart examples focus on resource provisioning but lack operational monitoring examples. This creates a gap for users who need to:

  • Monitor Fabric Capacity performance and utilization
  • Set up intelligent alerting for resource thresholds
  • Implement centralized logging for troubleshooting
  • Create real-time dashboards for operational insights

💡 Proposed Solution

Add a new quickstart example 801-monitoring-logging that includes:

Core Components

  • Log Analytics Workspace: Centralized log collection and analysis
  • Application Insights: Application performance monitoring
  • Azure Dashboard: Real-time metrics visualization
  • Alert Rules: Intelligent alerting for CPU, memory, and storage thresholds

Key Features

  • ✅ Configurable alert thresholds
  • ✅ Email and webhook notifications
  • ✅ Multi-environment support (dev/staging/prod)
  • ✅ Cost optimization features
  • ✅ Comprehensive testing (unit + acceptance)
  • ✅ Complete documentation with troubleshooting guide

Implementation Details

  • Follow existing project patterns and conventions
  • Include Terraform tests using TDD methodology
  • Provide example configurations and best practices
  • Support resource tagging and naming conventions

Expected Benefits

  • Enhanced operational visibility for Fabric deployments
  • Proactive issue detection and alerting
  • Reduced MTTR (Mean Time To Recovery)
  • Better resource utilization insights
  • Improved troubleshooting capabilities

Ready for Implementation

I have already implemented this solution and it's ready for review in the feature/operations-management branch.

…onitoring-logging)

- Implement complete monitoring stack with Log Analytics, Application Insights, and Azure Dashboard
- Add intelligent alerting system with email and webhook notifications
- Include CPU, memory, and storage utilization alerts with configurable thresholds
- Provide real-time dashboard with Fabric Capacity metrics visualization
- Add comprehensive unit and acceptance tests following TDD methodology
- Include complete documentation with architecture diagrams and troubleshooting guide
- Support multi-environment deployment with proper resource tagging
- Implement cost optimization features and security best practices
@shashax42 shashax42 requested a review from a team as a code owner September 16, 2025 03:51
@shashax42
Copy link
Author

@shashax42다음 기여자 라이선스 계약(CLA)을 읽어주세요. CLA에 동의하시는 경우, 아래 정보를 포함하여 회신해 주세요.

@microsoft-github-policy-service agree [company="{your company}"]

옵션:

  • (기본값 - 회사 미지정) 저는 제출물에 대한 지적 재산권을 단독으로 소유하며, 고용주를 위한 업무 과정에서 제출물을 만들지 않습니다.
@microsoft-github-policy-service agree
  • (회사에서 제공한 경우) 본인은 고용주를 대신하여 업무 과정에서 제출물을 작성합니다(또는 고용주가 계약 또는 관련 법률에 따라 제출물에 대한 지적 재산권을 보유합니다). 본인은 고용주로부터 고용주를 대신하여 제출물을 작성하고 본 계약을 체결할 수 있는 허가를 받았습니다. 아래 서명함으로써 정의된 "귀하"에는 본인과 고용주가 포함됩니다.
@microsoft-github-policy-service agree company="Microsoft"

기여자 라이선스 계약

@microsoft-github-policy-service agree [company="personal"]

@shashax42
Copy link
Author

@shashax42입력한 명령이 잘못되었습니다. 다시 시도해 주세요.

예를 들면 다음과 같습니다.

@microsoft-github-policy-service agree

그리고

@microsoft-github-policy-service agree company="your company"

@microsoft-github-policy-service agree
@microsoft-github-policy-service agree company="Personal"

@DariuszPorowski
Copy link
Member

@badeamarjieh @OrBaubergMicrosoft @Halamish51 PTAL for this PR, looks very interesting!

@shashax42 please rename 801 to 402, we keep 100-400 scale for complexity level indicator, this example fits into 400 level, and the next available number in-line is 2 :) thanks!

@shashax42 shashax42 changed the title feat: Add comprehensive Fabric monitoring and logging solution (801-m… feat: Add comprehensive Fabric monitoring and logging solution (402-m… Sep 17, 2025
- Change folder name from 801 to 402 to follow project complexity level conventions
- Update README.md title from '800 level' to '400 level'
- Address reviewer feedback from PR microsoft#143
@shashax42
Copy link
Author

@DariuszPorowski
Thank you for the feedback🙏I followed your suggestion and would appreciate it if you could take a look. Thank you✨

@DariuszPorowski DariuszPorowski changed the title feat: Add comprehensive Fabric monitoring and logging solution (402-m… feat(402-monitoring-logging): add comprehensive Fabric monitoring and logging solution Sep 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants