diff --git a/.github/workflows/use-visitor-counter.yml b/.github/workflows/use-visitor-counter.yml new file mode 100644 index 0000000..4aa2c96 --- /dev/null +++ b/.github/workflows/use-visitor-counter.yml @@ -0,0 +1,94 @@ +name: Use Visitor Counter Logic + +on: + pull_request: + branches: + - main + schedule: + - cron: '0 0 * * *' # Runs daily at midnight + workflow_dispatch: # Allows manual triggering + +permissions: + contents: write + pull-requests: write + +jobs: + update-visitor-count: + runs-on: ubuntu-latest + + steps: + - name: Checkout current repository + uses: actions/checkout@v4 + with: + fetch-depth: 0 + + - name: Shallow clone visitor counter logic + run: git clone --depth=1 https://github.com/brown9804/github-visitor-counter.git + + - name: Set up Node.js + uses: actions/setup-node@v4 + with: + node-version: '20' + + - name: Install dependencies for github-visitor-counter + run: | + cd github-visitor-counter + npm ci + + - name: Run visitor counter logic (updates markdown badges and metrics.json) + run: node github-visitor-counter/update_repo_views_counter.js + env: + TRAFFIC_TOKEN: ${{ secrets.TRAFFIC_TOKEN }} + REPO: ${{ github.repository }} + + - name: Move generated metrics.json to root + run: mv github-visitor-counter/metrics.json . + + - name: List files for debugging + run: | + ls -l + ls -l github-visitor-counter + + - name: Clean up visitor counter logic + run: rm -rf github-visitor-counter + + - name: Configure Git author + run: | + git config --global user.name "github-actions[bot]" + git config --global user.email "github-actions[bot]@users.noreply.github.com" + + - name: Commit and push changes (PR) + if: github.event_name == 'pull_request' + env: + TOKEN: ${{ secrets.GITHUB_TOKEN }} + run: | + git fetch origin + git checkout -b ${{ github.event.pull_request.head.ref }} origin/${{ github.event.pull_request.head.ref }} + git add "*.md" metrics.json + git commit -m "Update visitor count" || echo "No changes to commit" + git remote set-url origin https://x-access-token:${TOKEN}@github.com/${{ github.repository }} + git pull --rebase origin ${{ github.event.pull_request.head.ref }} || echo "No rebase needed" + git push origin HEAD:${{ github.event.pull_request.head.ref }} + + - name: Commit and push changes (non-PR) + if: github.event_name != 'pull_request' + env: + TOKEN: ${{ secrets.GITHUB_TOKEN }} + run: | + git fetch origin + git checkout ${{ github.event.pull_request.head.ref }} || git checkout -b ${{ github.event.pull_request.head.ref }} origin/${{ github.event.pull_request.head.ref }} + git add "*.md" metrics.json + git commit -m "Update visitor count" || echo "No changes to commit" + git remote set-url origin https://x-access-token:${TOKEN}@github.com/${{ github.repository }} + git pull --rebase origin ${{ github.event.pull_request.head.ref }} || echo "No rebase needed" + git push origin HEAD:${{ github.event.pull_request.head.ref }} + + - name: Create Pull Request (non-PR) + if: github.event_name != 'pull_request' + uses: peter-evans/create-pull-request@v6 + with: + token: ${{ secrets.GITHUB_TOKEN }} + branch: update-visitor-count + title: "Update visitor count" + body: "Automated update of visitor count" + base: main diff --git a/Cost-Management/BillingReport.md b/Cost-Management/BillingReport.md index 9428a05..cda510f 100644 --- a/Cost-Management/BillingReport.md +++ b/Cost-Management/BillingReport.md @@ -105,7 +105,9 @@ Last updated: 2025-05-02 image +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/Cost-Management/BudgetAlerts.md b/Cost-Management/BudgetAlerts.md index 99c3e50..72db7ec 100644 --- a/Cost-Management/BudgetAlerts.md +++ b/Cost-Management/BudgetAlerts.md @@ -63,7 +63,9 @@ Last updated: 2025-05-02 - Review cost-saving recommendations provided by Azure. - Implement suggested optimizations to reduce unnecessary spending. +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/Cost-Management/PricingOverview.md b/Cost-Management/PricingOverview.md index 448a085..1f41107 100644 --- a/Cost-Management/PricingOverview.md +++ b/Cost-Management/PricingOverview.md @@ -13,10 +13,10 @@ Last updated: 2025-03-21
List of References (Click to expand) -- [Fabric operations](https://learn.microsoft.com/en-us/fabric/enterprise/fabric-operations) -- [Microsoft Fabric pricing](https://azure.microsoft.com/en-us/pricing/details/microsoft-fabric/?cdn=disable) -- [Microsoft Fabric Monitoring Usage - Overview](https://github.com/MicrosoftCloudEssentials-LearningHub/Fabric-EnterpriseFramework/blob/main/Monitoring-Observability/MonitorUsage.md) -- [Steps to Configure Capacity Alerts - Overview](https://github.com/MicrosoftCloudEssentials-LearningHub/Fabric-EnterpriseFramework/blob/main/Monitoring-Observability/StepsCapacityAlert.md) +- [Fabric operations](https://learn.microsoft.com/en-us/fabric/enterprise/fabric-operations) +- [Microsoft Fabric pricing](https://azure.microsoft.com/en-us/pricing/details/microsoft-fabric/?cdn=disable) +- [Microsoft Fabric Monitoring Usage - Overview](https://github.com/MicrosoftCloudEssentials-LearningHub/Fabric-EnterpriseFramework/blob/main/Monitoring-Observability/MonitorUsage.md) +- [Steps to Configure Capacity Alerts - Overview](https://github.com/MicrosoftCloudEssentials-LearningHub/Fabric-EnterpriseFramework/blob/main/Monitoring-Observability/StepsCapacityAlert.md)
@@ -25,11 +25,11 @@ Last updated: 2025-03-21 - [Overview](#overview) - [Reservations & Capacity](#reservations--capacity) - - [Scope Assignment in Reservations](#scope-assignment-in-reservations) + - [Scope Assignment in Reservations](#scope-assignment-in-reservations) - [Additional Costs](#additional-costs) - [E.g F64](#eg-f64) - - [Included in F64 Reserved Capacity](#included-in-f64-reserved-capacity) - - [What’s NOT Included in the Flat Rate](#whats-not-included-in-the-flat-rate) + - [Included in F64 Reserved Capacity](#included-in-f64-reserved-capacity) + - [What’s NOT Included in the Flat Rate](#whats-not-included-in-the-flat-rate) @@ -50,9 +50,10 @@ Last updated: 2025-03-21 > The included storage in Microsoft Fabric primarily applies to **mirroring** across all F SKUs. This means that the free storage provided (e.g., 64 TB for F64) is specifically allocated for creating mirrored copies of your data to ensure redundancy and high availability.

> For other types of storage, such as general data storage or storage used by Data Factory and AI capabilities, you will be billed if you exceed the included storage or if compute capacity is paused.This applies to all F SKUs, from F2 to F2048. -https://github.com/user-attachments/assets/83447901-2227-4cf3-a89c-c8ee57d50009 + > Considerations: + - **Region and SKU Size**: The price of Microsoft Fabric services varies based on the region and the SKU size. For instance, the cost in North America is different from that in Europe. Additionally, different SKUs have specific rates. For example, an F256 SKU has a different rate compared to an F128 SKU. - **What is an SKU?**: SKU stands for **Stock Keeping Unit**. It's a unique identifier for each distinct product and service that can be purchased. In the context of Microsoft Fabric, SKUs represent different capacities or configurations of the service. For example, an F256 SKU indicates a specific capacity of 256 Compute Units (CU). - **What is a CU?**: CU stands for **Compute Unit**. It's a measure of the computing resources allocated to your service. Higher CU values indicate more computing power and capacity. For instance, an F256 SKU provides 256 CUs, which can handle more intensive workloads compared to an F128 SKU with 128 CUs. @@ -62,6 +63,7 @@ https://github.com/user-attachments/assets/83447901-2227-4cf3-a89c-c8ee57d50009 This flexibility allows you to optimize your Microsoft Fabric costs based on your specific requirements and usage patterns. Being clear about the sizes and regions helps ensure you get the best value for your reservation. > [!NOTE] +> > - `Capacity Units (CU)`: Measure of compute power within a SKU. Higher CUs provide more computational capacity.
> - `Power BI SKU`: Different SKUs (A, EM, P, F) cater to various needs from individual users to large enterprises.
> - `Power BI v-cores`: Virtual cores dedicated to Power BI operations, ensuring consistent performance.
@@ -94,6 +96,7 @@ This flexibility allows you to optimize your Microsoft Fabric costs based on you > Microsoft Fabric `Reservations are agreements` for a specific time period and compute capacity. Whether using the Pay-as-you-go model or reservations, you need to create the Microsoft Fabric Capacity within a resource group.

> Reservations in Azure, including Microsoft Fabric `reservations`, are `managed at the subscription level`. This means that the reserved capacity units (CUs) apply to the entire subscription, not to individual resource groups.
+> > - `Reservations`: Provide a `subscription-wide discount` for committing to a certain amount of capacity over a period of time.
> - `Capacity Creation`: You create and manage Fabric `capacities within specific resource groups`, but the `cost benefits from the reservation apply at the subscription level`. @@ -144,7 +147,7 @@ This flexibility allows you to optimize your Microsoft Fabric costs based on you - If your workloads **exceed 64 CUs**, you’ll be billed **pay-as-you-go** for the overage. - **Storage and networking** costs (e.g., OneLake storage, data egress) are **not included** in the reservation -### Included in F64 Reserved Capacity +### Included in F64 Reserved Capacity > These services are covered **as long as they stay within the 64 CU limit**: @@ -163,7 +166,6 @@ This flexibility allows you to optimize your Microsoft Fabric costs based on you > These are **billed separately** if they exceed the reserved CU pool or use **specialized compute**. These charges apply **only when usage exceeds the base F64 capacity or involves specialized compute paths**. - | **Service/Workload** | **Why It’s Extra** | |----------------------|--------------------| | **Data Movement (e.g., Copy activity)** | Uses additional compute beyond base CU allocation. | @@ -173,8 +175,9 @@ This flexibility allows you to optimize your Microsoft Fabric costs based on you | **Iterative Read/Write via Proxy** | Repeated access patterns through proxy connections are compute-intensive and billed separately. | | **Networking & Storage** | Not included in Fabric capacity; billed separately under Azure storage and data transfer pricing. | - +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/Deployment-Pipelines/README.md b/Deployment-Pipelines/README.md index c718826..45f7a0a 100644 --- a/Deployment-Pipelines/README.md +++ b/Deployment-Pipelines/README.md @@ -196,7 +196,9 @@ Steps to Set Up Incremental Refresh: 3. **Enable Incremental Refresh**: Right-click the query and select Incremental Refresh. Configure the settings, such as the DateTime column and the time range for data extraction. 4. **Publish the Dataflow**: Once configured, publish the dataflow. The dataflow will then automatically refresh the data incrementally based on the settings. +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/Deployment-Pipelines/samples/README.md b/Deployment-Pipelines/samples/README.md index 5db01b7..a412a84 100644 --- a/Deployment-Pipelines/samples/README.md +++ b/Deployment-Pipelines/samples/README.md @@ -12,7 +12,9 @@ Last updated: 2025-04-15 > In this folder, you'll find some sample files that we'll be using throughout the demo. > `These files will help us illustrate the process of creating a workspace, setting up a lakehouse, defining a dataset schema, generating reports with Copilot, creating a semantic model, and deploying through a pipeline`. +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/Deployment-Pipelines/samples/data/readme.md b/Deployment-Pipelines/samples/data/readme.md deleted file mode 100644 index 041ab01..0000000 --- a/Deployment-Pipelines/samples/data/readme.md +++ /dev/null @@ -1,2 +0,0 @@ - -Last updated: 2025-04-21 diff --git a/GitHub-Integration.md b/GitHub-Integration.md index 20d9303..3a3dddd 100644 --- a/GitHub-Integration.md +++ b/GitHub-Integration.md @@ -60,7 +60,9 @@ Last updated: 2025-04-21 > Click here to read more about [considerations and limitations](https://learn.microsoft.com/en-us/fabric/cicd/git-integration/git-get-started?tabs=azure-devops%2CAzure%2Ccommit-to-git#considerations-and-limitations). -
-

Total Visitors

- Visitor Count + +
+ Total views +

Refresh Date: 2025-07-17

+ diff --git a/Monitoring-Observability/MonitorUsage.md b/Monitoring-Observability/MonitorUsage.md index a4ff2c8..033ca85 100644 --- a/Monitoring-Observability/MonitorUsage.md +++ b/Monitoring-Observability/MonitorUsage.md @@ -288,7 +288,9 @@ Steps to Access Microsoft Purview via Audit Logs: image +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/Monitoring-Observability/StepsCapacityAlert.md b/Monitoring-Observability/StepsCapacityAlert.md index 7225135..dd4585b 100644 --- a/Monitoring-Observability/StepsCapacityAlert.md +++ b/Monitoring-Observability/StepsCapacityAlert.md @@ -47,7 +47,9 @@ Last updated: 2025-04-21 image +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/README.md b/README.md index 9dc3a11..5280967 100644 --- a/README.md +++ b/README.md @@ -238,7 +238,9 @@ Click to read more about [Microsoft Purview for Fabric - Overview](./Workloads-S - [Power Bi - Best Practices Overview](./Workloads-Specific/PowerBi/BestPractices.md) - [Purview - Best Practices Overview](./Workloads-Specific/Purview/BestPractices.md) +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/Security/CopyJobPermissions.md b/Security/CopyJobPermissions.md index 4482e49..d63c1ea 100644 --- a/Security/CopyJobPermissions.md +++ b/Security/CopyJobPermissions.md @@ -44,7 +44,9 @@ Last updated: 2025-05-08 image +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/Security/DashboardPermissions.md b/Security/DashboardPermissions.md index bde593e..f05c3e7 100644 --- a/Security/DashboardPermissions.md +++ b/Security/DashboardPermissions.md @@ -52,7 +52,9 @@ Last updated: 2025-05-08 image +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/Security/DataPipelinesPermissions.md b/Security/DataPipelinesPermissions.md index bbf0f27..2f29ec3 100644 --- a/Security/DataPipelinesPermissions.md +++ b/Security/DataPipelinesPermissions.md @@ -47,7 +47,9 @@ Last updated: 2025-05-08 image +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/Security/EventStreamPermissions.md b/Security/EventStreamPermissions.md index 9ce9881..c365b1c 100644 --- a/Security/EventStreamPermissions.md +++ b/Security/EventStreamPermissions.md @@ -48,7 +48,9 @@ Last updated: 2025-05-08 image +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/Security/HealthcareDataSolutionsPermissions.md b/Security/HealthcareDataSolutionsPermissions.md index 475b75a..f1af2b4 100644 --- a/Security/HealthcareDataSolutionsPermissions.md +++ b/Security/HealthcareDataSolutionsPermissions.md @@ -48,7 +48,9 @@ Last updated: 2025-05-08 image +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/Security/LakehousePermissions.md b/Security/LakehousePermissions.md index 306d066..489959c 100644 --- a/Security/LakehousePermissions.md +++ b/Security/LakehousePermissions.md @@ -98,7 +98,9 @@ Last updated: 2025-05-08 image +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/Security/README.md b/Security/README.md index f100e7d..7de808f 100644 --- a/Security/README.md +++ b/Security/README.md @@ -17,8 +17,10 @@ Last updated: 2025-05-08 - [Data Pipelines Permissions](./DataPipelinesPermissions.md): Data Pipelines - [Event Stream Permissions](./EventStreamPermissions.md): Event Stream - [Healthcare data solutions Permissions](./HealthcareDataSolutionsPermissions.md): Healthcare Data Solutions - + +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/Security/SemanticModelsPermissions.md b/Security/SemanticModelsPermissions.md index ffa72bf..ce79882 100644 --- a/Security/SemanticModelsPermissions.md +++ b/Security/SemanticModelsPermissions.md @@ -39,7 +39,9 @@ Last updated: 2025-05-08 | Allow recipients to build content with the data associated with this semantic model | Enables users to create reports, dashboards, and other content using the semantic model. | - `Power BI Reports`: Building visuals and dashboards.
- `Embedded Analytics`: Using the model in apps or portals.
- `Ad hoc Analysis`: Exploring data. | | Send an email notification | Sends an email to notify the recipient about the access granted. | - `Communication`: Ensuring users are informed of their new access.
- `Onboarding`: Helping users get started with the semantic model. | +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/Security/WarehousePermissions.md b/Security/WarehousePermissions.md index db33ceb..5ef931d 100644 --- a/Security/WarehousePermissions.md +++ b/Security/WarehousePermissions.md @@ -125,7 +125,9 @@ Last updated: 2025-05-08 image +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/Terraform/README.md b/Terraform/README.md index ff248f4..743a7c2 100644 --- a/Terraform/README.md +++ b/Terraform/README.md @@ -154,7 +154,9 @@ graph TD; image +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/Terraform/troubleshooting.md b/Terraform/troubleshooting.md index 57c8a3f..f77a4be 100644 --- a/Terraform/troubleshooting.md +++ b/Terraform/troubleshooting.md @@ -183,7 +183,9 @@ Error: Failed to get existing workspaces: Error retrieving keys for Storage Acco image

+
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/Workloads-Specific/DataEngineering/BestPractices.md b/Workloads-Specific/DataEngineering/BestPractices.md index 83a7f08..ecdcb55 100644 --- a/Workloads-Specific/DataEngineering/BestPractices.md +++ b/Workloads-Specific/DataEngineering/BestPractices.md @@ -25,7 +25,7 @@ Last updated: 2025-05-03 Centered Image
-| **Best Practice** | **Description** | **Example** | +| **Best Practice** | **Description**| **Example**| |------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Structured Lakehouse Organization** | Organize your data lakehouse into well-defined zones (raw, processed, and curated) that include optimized storage formats, clear partitioning schemes, metadata tagging, access controls, and lineage tracking. This approach not only simplifies data discovery and query performance but also ensures robust data governance, highlighting every transformation. Designing your storage with structured hierarchies and access layers helps maintain both flexibility and compliance while enabling efficient audits and troubleshooting. | Create dedicated directories where:
- **Bronze Layer** Holds ingested data in its original format with minimal transformations to preserve source fidelity.
- **Silver Layer** Contains data that has been cleansed, validated, and enriched.
- **Gold Layer** Delivers analytics-ready datasets using formats such as Parquet or Delta Lake, partitioned by key fields like date or region. Enhance these folders with metadata catalogs and role-based access to safeguard sensitive information and track data lineage from ingestion to consumption. | | **Well-Documented Notebooks** | Develop notebooks that are modular, well-structured, and version-controlled to ensure end-to-end transparency and reproducibility. Use rich markdown annotations to explain the rationale behind data ingestion, transformation logic, and analytical models. Embedding inline comments, headers, and detailed commit histories allows your team to understand the evolution of code and quickly troubleshoot issues. This meticulous documentation fosters collaboration, ensures best practices are followed, and supports seamless handoffs between team members. | Split notebooks into logical sections such as:
- **Data Ingestion:** Code to load raw data with validation checks.
- **Data Transformation:** Segments dedicated to cleaning, merging, and enriching data with clear explanations of business logic.
- **Analysis & Visualization:** Final processing that translates data into actionable insights.
Adopt a distributed version control system (e.g., Git) and use clear commit messages along with markdown cells that detail the purpose, changes, and expected outputs of each segment, ensuring that both current and future team members can understand and extend your work. | @@ -63,7 +63,9 @@ Last updated: 2025-05-03 +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/Workloads-Specific/DataFactory/BestPractices.md b/Workloads-Specific/DataFactory/BestPractices.md index ec69188..c450e76 100644 --- a/Workloads-Specific/DataFactory/BestPractices.md +++ b/Workloads-Specific/DataFactory/BestPractices.md @@ -474,7 +474,9 @@ graph TD image -
-

Total Visitors

- Visitor Count + +
+ Total views +

Refresh Date: 2025-07-17

+ diff --git a/Workloads-Specific/DataFactory/HowMonitorChanges.md b/Workloads-Specific/DataFactory/HowMonitorChanges.md index 197adb1..633680d 100644 --- a/Workloads-Specific/DataFactory/HowMonitorChanges.md +++ b/Workloads-Specific/DataFactory/HowMonitorChanges.md @@ -125,7 +125,9 @@ Last updated: 2025-04-21 image +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/Workloads-Specific/DataScience/AI_integration/README.md b/Workloads-Specific/DataScience/AI_integration/README.md index 4c332f4..b9fad47 100644 --- a/Workloads-Specific/DataScience/AI_integration/README.md +++ b/Workloads-Specific/DataScience/AI_integration/README.md @@ -397,7 +397,9 @@ Make sure to replace `"your_openai_api_key"`, `"https://your_openai_api_base/"`, pprint(dict(rm), indent=4) ``` +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/Workloads-Specific/DataScience/BestPractices.md b/Workloads-Specific/DataScience/BestPractices.md index 9e2ba79..539cc0b 100644 --- a/Workloads-Specific/DataScience/BestPractices.md +++ b/Workloads-Specific/DataScience/BestPractices.md @@ -54,7 +54,9 @@ Last updated: 2025-05-03 Click to read [Demonstration: Data Agents in Microsoft Fabric](./Data_Agents.md). +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/Workloads-Specific/DataScience/Data_Agents.md b/Workloads-Specific/DataScience/Data_Agents.md index 5149ce1..0ef5471 100644 --- a/Workloads-Specific/DataScience/Data_Agents.md +++ b/Workloads-Specific/DataScience/Data_Agents.md @@ -85,7 +85,9 @@ Key Features: | Can you highlight any correlations between variables? | image | | What are the outliers in this dataset? | image | +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/Workloads-Specific/DataScience/How_AutoML/README.md b/Workloads-Specific/DataScience/How_AutoML/README.md index 4eb0160..d03383e 100644 --- a/Workloads-Specific/DataScience/How_AutoML/README.md +++ b/Workloads-Specific/DataScience/How_AutoML/README.md @@ -20,7 +20,9 @@ Click to see notebook generated [Train a ML model with AutoML](./Train_MLmodel_A +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/Workloads-Specific/DataWarehouse/BestPractices.md b/Workloads-Specific/DataWarehouse/BestPractices.md index 009067d..39b3346 100644 --- a/Workloads-Specific/DataWarehouse/BestPractices.md +++ b/Workloads-Specific/DataWarehouse/BestPractices.md @@ -83,7 +83,9 @@ Create notebooks that are segmented into distinct sections: | **Mirrored Azure SQL Managed Instance** | Configure an Azure SQL Managed Instance in a mirrored setup using strategies like log shipping or transactional replication. Monitor key performance metrics to ensure that replication latency is minimal, and the mirror is capable of supporting a swift transition during outages or maintenance windows. | | **Mirrored Database** | Set up a mirrored database configuration that synchronizes periodically with a primary instance. Schedule automated tests and synchronization checks, and simulate failover events to validate that the data remains consistent, with built-in alerts and monitoring demonstrating the mirror’s readiness for production use. | +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/Workloads-Specific/DataWarehouse/Medallion_Architecture/README.md b/Workloads-Specific/DataWarehouse/Medallion_Architecture/README.md index ca1f672..861a6cd 100644 --- a/Workloads-Specific/DataWarehouse/Medallion_Architecture/README.md +++ b/Workloads-Specific/DataWarehouse/Medallion_Architecture/README.md @@ -302,7 +302,9 @@ VALUES image +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/Workloads-Specific/DataWarehouse/Medallion_Architecture/docs/README.md b/Workloads-Specific/DataWarehouse/Medallion_Architecture/docs/README.md index 189aa29..b9b8eda 100644 --- a/Workloads-Specific/DataWarehouse/Medallion_Architecture/docs/README.md +++ b/Workloads-Specific/DataWarehouse/Medallion_Architecture/docs/README.md @@ -12,3 +12,10 @@ Last updated: 2025-05-03 > You can use the [drawio template](./FabricMedallionArch.drawio) as guidance to create your solution diagram. image + + +
+ Total views +

Refresh Date: 2025-07-17

+
+ diff --git a/Workloads-Specific/PowerBi/BestPractices.md b/Workloads-Specific/PowerBi/BestPractices.md index cca9f6b..2095fee 100644 --- a/Workloads-Specific/PowerBi/BestPractices.md +++ b/Workloads-Specific/PowerBi/BestPractices.md @@ -165,7 +165,9 @@ From [Understand star schema and the importance for Power BI](https://learn.micr | **Deployment Pipelines via APIs** | Use the Power BI deployment pipelines APIs to automate report deployment steps and ensure quality across environments. | Implement automated deployments as described in [Automate deployment pipelines with APIs for Power BI items](https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/pipeline-automation). | | **Continuous Integration** | Incorporate quality gates and automated testing within your CI/CD process to catch issues early in the development cycle. | Utilize Git-based integration and automated tests as shown in [Power BI Desktop projects Azure DevOps integration](https://learn.microsoft.com/en-us/power-bi/developer/projects/projects-azdo) for best practices. | +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/Workloads-Specific/Purview/BestPractices.md b/Workloads-Specific/Purview/BestPractices.md index 933455a..15ea1d4 100644 --- a/Workloads-Specific/Purview/BestPractices.md +++ b/Workloads-Specific/Purview/BestPractices.md @@ -156,7 +156,9 @@ Last updated: 2025-05-05 > Encourage data producers to endorse trusted datasets and models. Use tags and descriptions to improve discoverability and promote reuse. This builds a culture of data trust and reduces duplication. Click [Govern your Fabric data](https://learn.microsoft.com/en-us/fabric/governance/onelake-catalog-govern) +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/Workloads-Specific/Purview/PurviewforFabric.md b/Workloads-Specific/Purview/PurviewforFabric.md index c5d1099..763b00e 100644 --- a/Workloads-Specific/Purview/PurviewforFabric.md +++ b/Workloads-Specific/Purview/PurviewforFabric.md @@ -115,7 +115,9 @@ graph TD | **Elastic Data Map Utilization** | Efficiently manage capacity units to optimize costs. | - **Monitor Usage**: Regularly monitor capacity unit usage to ensure efficient allocation and avoid over-provisioning.
- **Scale Appropriately**: Scale capacity units based on actual usage patterns to optimize costs. | | **API Call Management** | Minimize unnecessary API calls to reduce costs. | - **Optimize API Usage**: Minimize unnecessary API calls by caching results and reusing data where possible.
- **Batch API Requests**: Group API requests to reduce the number of individual calls, optimizing cost per API call. | +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/Workloads-Specific/RealTimeIntelligence/BestPractices.md b/Workloads-Specific/RealTimeIntelligence/BestPractices.md index 99a3fc8..0fcbe84 100644 --- a/Workloads-Specific/RealTimeIntelligence/BestPractices.md +++ b/Workloads-Specific/RealTimeIntelligence/BestPractices.md @@ -55,7 +55,9 @@ Click to read [Demonstration: Automating Pipeline Execution with Activator](./Fa +
-

Total Visitors

- Visitor Count + Total views +

Refresh Date: 2025-07-17

+ diff --git a/metrics.json b/metrics.json new file mode 100644 index 0000000..8665541 --- /dev/null +++ b/metrics.json @@ -0,0 +1,37 @@ +[ + { + "date": "2025-07-07", + "count": 330, + "uniques": 20 + }, + { + "date": "2025-07-08", + "count": 159, + "uniques": 6 + }, + { + "date": "2025-07-10", + "count": 482, + "uniques": 1 + }, + { + "date": "2025-07-11", + "count": 170, + "uniques": 4 + }, + { + "date": "2025-07-12", + "count": 7, + "uniques": 1 + }, + { + "date": "2025-07-14", + "count": 130, + "uniques": 2 + }, + { + "date": "2025-07-15", + "count": 2, + "uniques": 1 + } +] \ No newline at end of file