There are three types of Application Insights availability tests:
URL ping test: a simple test that you can create in the Azure portal.
Multi-step web test
Custom Track Availability Tests
Note: After you've deployed your web app/website, you can set up recurring tests to monitor availability and responsiveness. Azure Application Insights sends web requests to your application at regular intervals from points around the world. It can alert you if your application isn't responding, or if it responds too slowly.
You can set up availability tests for any HTTP or HTTPS endpoint that is accessible from the public internet.
You don't have to make any changes to the website you're testing. In fact, it doesn't even have to be a site you own. You can test the availability of a REST API that your service depends on.
Reference:
https://docs.microsoft.com/en-us/azure/azure-monitor/app/monitor-web-app-availability#create-a-url-ping-test

https://docs.microsoft.com/en-us/azure/devops/pipelines/troubleshooting/troubleshooting

See explanation below
Explanation:
Step 1: Access Azure DevOps
* Open your browser and navigate to https://aex.dev.azure.com.
* You will be prompted to sign in. Enter the following credentials:
* Username: [email protected]
* Password: aFpJ2j-6M!
* Click Next or Sign in to proceed.
Note: If you see any Microsoft security challenge (like phone or email verification), follow the instructions to complete it.
Step 2: Sign Up for Azure DevOps
* After signing in, you'll see a prompt to sign up for Azure DevOps.
* Use the default settings provided by Azure DevOps for the sign-up process (region, default name, etc.).
* Click Continue or Start free with Azure DevOps.
An Azure DevOps Organization is a container for your projects and resources. Default settings are usually fine for new organizations.
Step 3: Create the Organization
* Enter a name for your organization. Azure DevOps will suggest a default name (like yourname or org- name), but you can change it if you prefer.
* Verify the region is correct.
* Click Continue to create the organization.
Your Azure DevOps organization is now created. It's the top-level container for all your projects.
Step 4: Create a Private Project Named Project1
* In your Azure DevOps portal, find the "New Project" button and click it.
* Enter the following details:
* Project Name: Project1
* Description: (optional)
* Visibility: Private
* Click Create.
A private project means that only users you add can see or access it. This is important for security and privacy.
Step 5: Enforce Maximum File Size for Repositories
By default, Azure DevOps allows files up to 100 MB to be pushed. To ensure the maximum file size for repositories in Project1 is 2 MB, you can enforce this using a pipeline validation.
Azure DevOps does not provide a direct setting for file size limits. However, you can create a pipeline to validate file size on pull requests and block changes if a file exceeds 2 MB.
Here's how to do it:
Option 1: Enforce with a pipeline validation for pull requests
* In your Project1, create a new pipeline.
* Use the following YAML for the pipeline:
yaml
Copy
trigger: none
pr:
branches:
include:
- "*"
jobs:
- job: CheckFileSize
pool:
vmImage: 'ubuntu-latest'
steps:
- script: |
echo "Checking file sizes in the PR..."
git fetch origin +refs/pull/*/merge:refs/remotes/origin/pr/*
large_files=$(git diff --cached --name-only | xargs -I{} du -b {} | awk '$1 > 2097152 {print $2}') if [ -n "$large_files" ]; then echo "Error: The following files exceed 2 MB:" echo "$large_files" exit 1 fi displayName: 'Check file sizes in PR' This pipeline will:
* Run on pull requests only.
* Check the size of all files in the pull request.
* If any file is larger than 2 MB (2,097,152 bytes), it will fail the pipeline and block the PR.
Option 2: Local Git configuration (for each developer)
On each developer's machine, run this command in their local repository:
bash
Copy
git config --local core.bigFileThreshold 2M
This limits the file threshold for checkout, but does not prevent large files from being pushed. Using the pipeline validation (Option 1) is more secure for team environments.