Merge pull request #24 from MicrosoftCloudEssentials-LearningHub/changing-counter

changing counter type + cleaning format

Author: brown9804

.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

Cost-Management/BillingReport.md

@@ -105,7 +105,9 @@ Last updated: 2025-05-02
 
       <img width="550" alt="image" src="https://github.com/user-attachments/assets/f677d4b9-882e-4893-9624-a0cad7624d73">
 
+<!-- START BADGE -->
 <div align="center">
-  <h3 style="color: #4CAF50;">Total Visitors</h3>
-  <img src="https://profile-counter.glitch.me/brown9804/count.svg" alt="Visitor Count" style="border: 2px solid #4CAF50; border-radius: 5px; padding: 5px;"/>
+  <img src="https://img.shields.io/badge/Total%20views-63-limegreen" alt="Total views">
+  <p>Refresh Date: 2025-07-17</p>
 </div>
+<!-- END BADGE -->

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.
 
+<!-- START BADGE -->
 <div align="center">
-  <h3 style="color: #4CAF50;">Total Visitors</h3>
-  <img src="https://profile-counter.glitch.me/brown9804/count.svg" alt="Visitor Count" style="border: 2px solid #4CAF50; border-radius: 5px; padding: 5px;"/>
+  <img src="https://img.shields.io/badge/Total%20views-63-limegreen" alt="Total views">
+  <p>Refresh Date: 2025-07-17</p>
 </div>
+<!-- END BADGE -->

Cost-Management/PricingOverview.md

@@ -13,10 +13,10 @@ Last updated: 2025-03-21
 <details>
 <summary><b>List of References </b> (Click to expand)</summary>
 
--  [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)
 
 </details>
 
@@ -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)
 
 </details>
 
@@ -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. <br/> <br/>
 > 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
+<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. <br/>
 > - `Power BI SKU`: Different SKUs (A, EM, P, F) cater to various needs from individual users to large enterprises. <br/>
 > - `Power BI v-cores`: Virtual cores dedicated to Power BI operations, ensuring consistent performance. <br/>
@@ -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. <br/> <br/>
 > 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. <br/>
+>
 > - `Reservations`: Provide a `subscription-wide discount` for committing to a certain amount of capacity over a period of time. <br/>
 > - `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. |
 
-
+<!-- START BADGE -->
 <div align="center">
-  <h3 style="color: #4CAF50;">Total Visitors</h3>
-  <img src="https://profile-counter.glitch.me/brown9804/count.svg" alt="Visitor Count" style="border: 2px solid #4CAF50; border-radius: 5px; padding: 5px;"/>
+  <img src="https://img.shields.io/badge/Total%20views-63-limegreen" alt="Total views">
+  <p>Refresh Date: 2025-07-17</p>
 </div>
+<!-- END BADGE -->

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.
 
+<!-- START BADGE -->
 <div align="center">
-  <h3 style="color: #4CAF50;">Total Visitors</h3>
-  <img src="https://profile-counter.glitch.me/brown9804/count.svg" alt="Visitor Count" style="border: 2px solid #4CAF50; border-radius: 5px; padding: 5px;"/>
+  <img src="https://img.shields.io/badge/Total%20views-63-limegreen" alt="Total views">
+  <p>Refresh Date: 2025-07-17</p>
 </div>
+<!-- END BADGE -->

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`.
 
+<!-- START BADGE -->
 <div align="center">
-  <h3 style="color: #4CAF50;">Total Visitors</h3>
-  <img src="https://profile-counter.glitch.me/brown9804/count.svg" alt="Visitor Count" style="border: 2px solid #4CAF50; border-radius: 5px; padding: 5px;"/>
+  <img src="https://img.shields.io/badge/Total%20views-63-limegreen" alt="Total views">
+  <p>Refresh Date: 2025-07-17</p>
 </div>
+<!-- END BADGE -->

Deployment-Pipelines/samples/data/readme.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).
 
- <div align="center">
-  <h3 style="color: #4CAF50;">Total Visitors</h3>
-  <img src="https://profile-counter.glitch.me/brown9804/count.svg" alt="Visitor Count" style="border: 2px solid #4CAF50; border-radius: 5px; padding: 5px;"/>
+<!-- START BADGE -->
+<div align="center">
+  <img src="https://img.shields.io/badge/Total%20views-63-limegreen" alt="Total views">
+  <p>Refresh Date: 2025-07-17</p>
 </div>
+<!-- END BADGE -->

GitHub-Integration.md

@@ -288,7 +288,9 @@ Steps to  Access Microsoft Purview via Audit Logs:
 
       <img width="550" alt="image" src="https://github.com/user-attachments/assets/90730142-2a56-43af-a6e5-6c3aa5deddff">
 
+<!-- START BADGE -->
 <div align="center">
-  <h3 style="color: #4CAF50;">Total Visitors</h3>
-  <img src="https://profile-counter.glitch.me/brown9804/count.svg" alt="Visitor Count" style="border: 2px solid #4CAF50; border-radius: 5px; padding: 5px;"/>
+  <img src="https://img.shields.io/badge/Total%20views-63-limegreen" alt="Total views">
+  <p>Refresh Date: 2025-07-17</p>
 </div>
+<!-- END BADGE -->

Monitoring-Observability/MonitorUsage.md

@@ -47,7 +47,9 @@ Last updated: 2025-04-21
 
 <img width="700" alt="image" src="https://github.com/user-attachments/assets/308e372d-48de-46f4-9138-984e15b5fd24">
 
+<!-- START BADGE -->
 <div align="center">
-  <h3 style="color: #4CAF50;">Total Visitors</h3>
-  <img src="https://profile-counter.glitch.me/brown9804/count.svg" alt="Visitor Count" style="border: 2px solid #4CAF50; border-radius: 5px; padding: 5px;"/>
+  <img src="https://img.shields.io/badge/Total%20views-63-limegreen" alt="Total views">
+  <p>Refresh Date: 2025-07-17</p>
 </div>
+<!-- END BADGE -->