diff --git a/Monitoring-Observability/FabricActivatorRulePipeline/GeneratesRandomData.ipynb b/Monitoring-Observability/FabricActivatorRulePipeline/GeneratesRandomData.ipynb
new file mode 100644
index 0000000..1b00089
--- /dev/null
+++ b/Monitoring-Observability/FabricActivatorRulePipeline/GeneratesRandomData.ipynb
@@ -0,0 +1 @@
+{"cells":[{"cell_type":"code","source":["# Generates Dummy json file in Files/\n","\n","# Import necessary libraries\n","from pyspark.sql import SparkSession\n","from pyspark.sql.types import *\n","import random\n","from datetime import datetime, timedelta\n","\n","# Initialize Spark session (if not already initialized)\n","spark = SparkSession.builder.appName(\"GenerateRandomData\").getOrCreate()\n","\n","# Function to generate random data\n","def generate_random_data(num_entries):\n"," data = []\n"," for i in range(1, num_entries + 1):\n"," name = f\"User{i}\"\n"," entry = {\n"," \"id\": i,\n"," \"name\": name,\n"," \"age\": random.randint(18, 65),\n"," \"email\": f\"{name.lower()}@example.com\",\n"," \"created_at\": (datetime.now() - timedelta(days=random.randint(0, 365))).strftime(\"%Y-%m-%d %H:%M:%S\")\n"," }\n"," data.append(entry)\n"," return data\n","\n","# Generate 10 random entries\n","random_data = generate_random_data(10)\n","\n","# Define schema for the DataFrame\n","schema = StructType([\n"," StructField(\"id\", IntegerType(), True),\n"," StructField(\"name\", StringType(), True),\n"," StructField(\"age\", IntegerType(), True),\n"," StructField(\"email\", StringType(), True),\n"," StructField(\"created_at\", StringType(), True)\n","])\n","\n","# Create a DataFrame from the random data\n","df_random_data = spark.createDataFrame(random_data, schema=schema)\n","\n","# Write the DataFrame to the Lakehouse in the specified path\n","output_path = \"abfss://{WORKSPACE-NAME}@onelake.dfs.fabric.microsoft.com/raw_Bronze.Lakehouse/Files/random_data\" # Replace {WORKSPACE-NAME}\n","df_random_data.write.format(\"delta\").mode(\"overwrite\").save(output_path)\n","\n","print(f\"Random data has been saved to the Lakehouse at '{output_path}'.\")"],"outputs":[],"execution_count":null,"metadata":{"microsoft":{"language":"python","language_group":"synapse_pyspark"}},"id":"8d820f25-3c2e-45b3-8a08-af78f0d45e1d"}],"metadata":{"kernel_info":{"name":"synapse_pyspark"},"kernelspec":{"name":"synapse_pyspark","language":"Python","display_name":"Synapse PySpark"},"language_info":{"name":"python"},"microsoft":{"language":"python","language_group":"synapse_pyspark","ms_spell_check":{"ms_spell_check_language":"en"}},"nteract":{"version":"nteract-front-end@1.0.0"},"spark_compute":{"compute_id":"/trident/default","session_options":{"conf":{"spark.synapse.nbs.session.timeout":"1200000"}}},"dependencies":{}},"nbformat":4,"nbformat_minor":5}
diff --git a/Monitoring-Observability/FabricActivatorRulePipeline/README.md b/Monitoring-Observability/FabricActivatorRulePipeline/README.md
new file mode 100644
index 0000000..01a5c2a
--- /dev/null
+++ b/Monitoring-Observability/FabricActivatorRulePipeline/README.md
@@ -0,0 +1,131 @@
+# Microsoft Fabric: Automating Pipeline Execution with Activator
+
+Costa Rica
+
+[](https://github.com/)
+[brown9804](https://github.com/brown9804)
+
+Last updated: 2025-04-15
+
+----------
+
+> This process shows how to set up Microsoft Fabric Activator to automate workflows by detecting file creation events in a storage system and triggering another pipeline to run.
+> 1. **First Pipeline**: The process starts with a pipeline that ends with a `Copy Data` activity. This activity uploads data into the `Lakehouse`.
+> 2. **Event Stream Setup**: An `Event Stream` is configured in Activator to monitor the Lakehouse for file creation or data upload events.
+> 3. **Triggering the Second Pipeline**: Once the event is detected (e.g., a file is uploaded), the Event Stream triggers the second pipeline to continue the workflow.
+
+
+List of References (Click to expand)
+
+- [Activate Fabric items](https://learn.microsoft.com/en-us/fabric/real-time-intelligence/data-activator/activator-trigger-fabric-items)
+- [Create a rule in Fabric Activator](https://learn.microsoft.com/en-us/fabric/real-time-intelligence/data-activator/activator-create-activators)
+
+
+
+
+List of Content (Click to expand)
+
+ - [Set Up the First Pipeline](#set-up-the-first-pipeline)
+ - [Configure Activator to Detect the Event](#configure-activator-to-detect-the-event)
+ - [Set Up the Second Pipeline](#set-up-the-second-pipeline)
+ - [Define the Rule in Activator](#define-the-rule-in-activator)
+ - [Test the Entire Workflow](#test-the-entire-workflow)
+ - [Troubleshooting If Needed](#troubleshooting-if-needed)
+
+
+
+> [!NOTE]
+> This code generates random data with fields such as id, name, age, email, and created_at, organizes it into a PySpark DataFrame, and saves it to a specified Lakehouse path using the Delta format. Click here to see the [example script](./GeneratesRandomData.ipynb)
+
+https://github.com/user-attachments/assets/95206bf3-83a7-42c1-b501-4879df22ef7d
+
+## Set Up the First Pipeline
+
+1. **Create the Pipeline**:
+ - In [Microsoft Fabric](https://app.fabric.microsoft.com/), create the first pipeline that performs the required tasks.
+ - Add a `Copy Data` activity as the final step in the pipeline.
+
+2. **Generate the Trigger File**:
+ - Configure the `Copy Data` activity to create a trigger file in a specific location, such as `Azure Data Lake Storage (ADLS)` or `OneLake`.
+ - Ensure the file name and path are consistent and predictable (e.g., `trigger_file.json` in a specific folder).
+3. **Publish and Test**: Publish the pipeline and test it to ensure the trigger file is created successfully.
+
+ https://github.com/user-attachments/assets/798a3b12-c944-459d-9e77-0112b5d82831
+
+## Configure Activator to Detect the Event
+
+> [!TIP]
+> Event options:
+
+https://github.com/user-attachments/assets/282fae9b-e1c6-490d-bd23-9ed9bdf6105d
+
+1. **Set Up an Event**:
+ - Create a new event to monitor the location where the trigger file is created (e.g., ADLS or OneLake). Click on `Real-Time`:
+
+ 
+
+ - Choose the appropriate event type, such as `File Created`.
+
+ 
+
+ 
+
+ - Add a source:
+
+ 
+
+ 
+
+ https://github.com/user-attachments/assets/43a9654b-e8d0-44da-80b9-9f528483fa3b
+
+2. **Test Event Detection**:
+ - Save the event and test it by manually running the first pipeline to ensure Activator detects the file creation.
+ - Check the **Event Details** screen in Activator to confirm the event is logged.
+
+ https://github.com/user-attachments/assets/6b21194c-54b4-49de-9294-1bf78b1e5acd
+
+## Set Up the Second Pipeline
+
+1. **Create the Pipeline**:
+ - In Microsoft Fabric, create the second pipeline that performs the next set of tasks.
+ - Ensure it is configured to accept external triggers.
+2. **Publish the Pipeline**: Publish the second pipeline and ensure it is ready to be triggered.
+
+ https://github.com/user-attachments/assets/5b630579-a0ec-4d5b-b973-d9b4fdd8254c
+
+## Define the Rule in Activator
+
+1. **Setup the Activator**:
+
+ https://github.com/user-attachments/assets/7c88e080-d5aa-4920-acd6-94c2e4ae0568
+
+2. **Create a New Rule**:
+ - In `Activator`, create a rule that responds to the event you just configured.
+ - Set the condition to match the event details (e.g., file name, path, or metadata).
+3. **Set the Action**:
+ - Configure the rule to trigger the second pipeline.
+ - Specify the pipeline name and pass any required parameters.
+3. **Save and Activate**:
+ - Save the rule and activate it.
+ - Ensure the rule is enabled and ready to respond to the event.
+
+ https://github.com/user-attachments/assets/5f139eeb-bab0-4d43-9f22-bbe44503ed75
+
+## Test the Entire Workflow
+
+1. **Run the First Pipeline**: Execute the first pipeline and verify that the trigger file is created.
+2. **Monitor Activator**: Check the `Event Details` and `Rule Activation Details` in Activator to ensure the event is detected and the rule is activated.
+3. **Verify the Second Pipeline**: Confirm that the second pipeline is triggered and runs successfully.
+
+ https://github.com/user-attachments/assets/0a1dab70-2317-4636-b0be-aa0cb301b496
+
+## Troubleshooting (If Needed)
+- If the second pipeline does not trigger:
+ 1. Double-check the rule configuration in Activator.
+ 2. Review the logs in Activator for any errors or warnings.
+
+
+
Total Visitors
+
+
+> - **Adjustments**: You can adjust the threshold and recipients at any time based on your needs.
+
+ | **Notification Setting** | **Value** |
+ |--------------------------|-----------|
+ | **Threshold** | 80% |
+ | **Recipients** | Capacity admins, Specific contacts |
+
+
+1. Go to the [Microsoft Fabric service](https://app.fabric.microsoft.com/) and sign in with your admin credentials.
+2. **Access the Admin Portal**:
+ - Click on the `Settings` gear icon in the top right corner.
+ - Select `Admin Portal` from the dropdown menu.
+
+ 
+
+3. **Navigate to Capacity Settings**:
+ - In the Admin Portal, go to the `Capacity settings` section.
+ - Select the capacity you want to configure notifications for.
+
+ 
+
+4. **Configure Notifications**:
+ - Expand the `Notifications` section.
+ - In the `Send notifications when` field, set the threshold to `80%`. This will trigger an alert when your capacity usage reaches 80% of the available CUs.
+ - You can also configure additional notifications for other thresholds if needed.
+5. **Specify Recipients**:
+ - In the **Send notifications to** field, select who should receive the notifications:
+ - **Capacity admins**: Email notifications will be sent to all admins of this capacity.
+ - **These contacts**: Enter the email addresses of specific contacts who should receive the notifications.
+6. **Apply Changes**: Click `Apply` to save the notification settings.
+
+ 
+
+> Find below an example of the email format:
+
+
+
+
+
Total Visitors
+
+
List of References (Click to expand)
-
+
+- [Microsoft Fabric adoption roadmap maturity levels](https://learn.microsoft.com/en-us/power-bi/guidance/fabric-adoption-roadmap-maturity-levels?context=%2Ffabric%2Fcontext%2Fcontext)
+- [What is workspace monitoring (preview)?](https://learn.microsoft.com/en-us/fabric/fundamentals/workspace-monitoring-overview)
+- [Azure Well-Architected Framework for data workloads](https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/scenarios/cloud-scale-analytics/well-architected-framework)
Table of Content (Click to expand)
-
+
+- [Prerequisites](#prerequisites)
+- [Infrastructure as Code IaC](#infrastructure-as-code-iac)
+- [Source Control Integration](#source-control-integration)
+- [Security](#security)
+- [Networking](#networking)
+- [Monitoring and Observability](#monitoring-and-observability)
@@ -136,11 +145,11 @@ Last updated: 2025-04-15
## Monitoring and Observability
-- **Microsoft [Fabric Capacity Metrics](https://github.com/MicrosoftCloudEssentials-LearningHub/Fabric-EnterpriseFramework/blob/main/Monitoring-Observability.md#microsoft-fabric-capacity-metrics-app) app**: Used for monitoring and managing capacity metrics.
-- **Admin Monitoring**: Configure and use the [Admin Monitoring Workspace](https://github.com/MicrosoftCloudEssentials-LearningHub/Fabric-EnterpriseFramework/blob/main/Monitoring-Observability.md#admin-monitoring) for custom reporting on system performance and usage.
-- **Monitor Hub**: Access and utilize the [Monitor Hub](https://github.com/MicrosoftCloudEssentials-LearningHub/Fabric-EnterpriseFramework/blob/main/Monitoring-Observability.md#monitor-hub) for centralized log and metric monitoring, and extend activity history of the data platform.
-- **Event Hub Integration**: Use Event Hub to capture and analyze events for real-time monitoring. For example, leverage it for [automating pipeline execution with Activator]()
-- **Alerting**: Configure alerts for critical events and thresholds to ensure timely responses to issues. For example, [Steps to Configure Capacity Alerts]()
+- **Microsoft [Fabric Capacity Metrics](https://github.com/MicrosoftCloudEssentials-LearningHub/Fabric-EnterpriseFramework/blob/main/Monitoring-Observability/README.md#microsoft-fabric-capacity-metrics-app) app**: Powerful tool for administrators to `monitor and manage their capacity usage`. It provides detailed insights into `capacity utilization, throttling, and system events, helping to optimize performance and resource allocation`. By tracking these metrics, admins can make informed decisions to ensure efficient use of resources.
+- **Admin Monitoring**: Configure and use the [Admin Monitoring Workspace](https://github.com/MicrosoftCloudEssentials-LearningHub/Fabric-EnterpriseFramework/blob/main/Monitoring-Observability/README.md#admin-monitoring) it's a centralized hub for `tracking and analyzing usage metrics across the organization`. It includes `pre-built reports and semantic models that provide insights into feature adoption, performance, and compliance`. This workspace helps administrators maintain the health and efficiency of their Fabric environment by offering a comprehensive `view of usage patterns and system events`.
+- **Monitor Hub**: Access and utilize the [Monitor Hub](https://github.com/MicrosoftCloudEssentials-LearningHub/Fabric-EnterpriseFramework/blob/main/Monitoring-Observability/README.md#monitor-hub). Allows users to `view and track the status of activities across all workspaces they have permissions for`. It provides a detailed overview of operations, `including dataset refreshes, Spark job runs, and other activities`. With features like historical views, customizable displays, and filtering options, the Monitor Hub helps ensure smooth operations and timely interventions when needed.
+- **Event Hub Integration**: Use Event Hub to capture and analyze events for real-time monitoring. For example, leverage it for [Automating pipeline execution with Activator](./Monitoring-Observability/FabricActivatorRulePipeline/)
+- **Alerting**: Configure alerts for critical events and thresholds to ensure timely responses to issues. For example, [Steps to Configure Capacity Alerts](./Monitoring-Observability/StepsCapacityAlert.md)
Total Visitors