Configuration Guide for External Service Incident Azure Monitor on the Elven Platform

The External Services Center of the Elven Platform is the bridge that connects you to the best tools on the market to monitor, manage, and resolve incidents in a simple and efficient way. Through it, you can integrate Azure Monitor with the Elven Platform, allowing the reception of event notifications related to incidents directly on the platform. This enables you to monitor and analyze your applications and services from an Incident Management perspective, using the best practices and methodologies available, all in one place.

API Token

To integrate the Elven Platform with Azure Monitor, you need to create an API Token. This unique key is essential for the two platforms to connect securely, ensuring reliable and authenticated information exchange. Simply access the Organization Settings of the Elven Platform, navigate to the API section, and generate it.

Creating an API Token

• In the top menu, under your user configuration section, click on Organization Settings.

• In the API tab, click the + button to create a new API Token.

Accessing External Service Incident Azure Monitor

On the Elven Platform, in the top menu, click on Services Hub. Then, look for the Incident Azure Monitor option and click on it. In the form that appears, start by filling in the External Service Name field, which will be the name of the external service, and define the Responders, that is, the people or teams who will receive notifications related to this service. After that, click CREATE to proceed. This action will create the initial record of your external service.

Registering the Microsoft Insights Provider

To ensure that your integration with the Elven Platform works correctly, the first step is to activate the required provider in Azure. Access the Azure Portal and go to the Subscriptions section, where you can view and manage your Subscriptions. If you prefer a shortcut, just use the search bar at the top of the page and type Subscriptions. Then, select the Subscription you want to work with. If more than one is available, choose the one that matches your project.

Inside the Subscription page, in the side menu, click on Resource Providers. This area allows you to activate and manage essential resource providers for Azure services. To quickly find what we need, type microsoft.insights in the search bar. Once it appears in the list, click on it and press the Register button. This process will activate the provider responsible for monitoring services, ensuring that your incident notifications are correctly sent to the Elven Platform. After the registration is confirmed, your Subscription will be ready for integration, allowing you to proceed with the configuration in Azure Monitor.

Configuring Webhooks in Azure Monitor

Setting up a Webhook in Azure Monitor for integration with the Elven Platform is a simple and essential process to ensure your alerts are received efficiently. To begin, access the Azure Portal and, in the side menu, look for the Monitor option. Within this section, click on Alerts and then go to the Action Groups tab. Here, you can create, view, and configure action groups that define how Azure will respond to triggered alerts. This step is crucial to ensure that notifications are correctly delivered to the Elven Platform.

Now, let’s create a new Action Group. Click on Create and select an existing Resource Group or create a new one to organize your resources efficiently. Then, define a clear and intuitive name for the Action Group, something that makes its purpose easy to identify. With the group created, it’s time to configure the actions that will be executed when an alert is triggered. Go to the Actions tab, choose the Webhook option, and enter the webhook URL generated by the Elven Platform. This URL will serve as the communication channel between Azure Monitor and the platform, ensuring that all notifications are sent correctly.

To better organize your alerts or events, you can add tags that help with identifying and managing resources within Azure. After defining the tags, click on Review + Create to review all settings before finalizing. If everything is correct, click Create to complete the process. Done! Your Action Group has been successfully created, and now Azure Monitor alerts will be automatically sent to the Elven Platform, ensuring an efficient and well-structured notification flow.

Testing the Integration Between Azure Monitor and the Elven Platform

With the Webhook configuration completed, it’s important to test if everything is working correctly. To do this, click on the newly created Action Group and go to the Test tab. This test will allow you to validate whether notifications are being properly sent to the Elven Platform. Within this section, select the Availability test alert option, which will help simulate an alert and verify the integration.

Now, click on Test and wait for the result. If everything is configured correctly, the notification will be successfully sent to the Elven Platform. To ensure the notification was actually received, access the platform and check if it arrived as expected. If everything is fine, click Done to complete the process. Done! Your Webhook is now active and working perfectly, ensuring that Azure Monitor notifications are delivered quickly and efficiently.

Additional Security and Performance Settings

• IP Whitelist: API communication can be configured to allow only authorized IPs. To enable or modify this setting, contact Elven Platform support.

• Rate Limiting: The default request limiting time is 5 minutes, but it can be adjusted as needed. For changes, contact Elven Platform support.

These settings ensure greater security and control over the data traffic between the integrated systems.

Glossary of Technical Terms

Action Group: A group in Azure Monitor that defines how the platform will respond to triggered alerts. It can include email notifications, automations, and webhook integrations.

API Token: A unique authentication key used to securely connect the Elven Platform to Azure Monitor, ensuring authenticated information exchange.

External Service: A feature in the Elven Platform that receives and manages incident or alert notifications from external services, enabling centralized monitoring.

Microsoft.Insights: An Azure provider responsible for monitoring and analytics services. It must be activated for the integration between Azure Monitor and the Elven Platform to work correctly.

Monitor (Azure Monitor): An Azure service that collects, analyzes, and responds to metrics and logs from cloud resources, allowing alert creation and integration with other platforms.

Resource Group: A logical container in Azure used to organize and manage resources, making infrastructure administration and security easier.

Resource Provider: A component in Azure that manages specific resources within a subscription. For integration with the Elven Platform, the Microsoft.Insights provider must be active.

Responders: People or teams configured to receive incident notifications generated by Azure Monitor within the Elven Platform.

Subscription: An Azure subscription that defines a management scope for resources and services used within the platform.

Tags: Labels used to organize and identify resources in Azure, making it easier to manage and track alerts and events.

Test (Integration Test): A process to validate communication between Azure Monitor and the Elven Platform, ensuring alerts are received correctly.

Webhook: An endpoint configured to receive automatic notifications from Azure Monitor and send events directly to the Elven Platform, ensuring continuous and real-time integration.

IP Whitelist: A list of authorized IP addresses for API communication, increasing security in data exchange between the Elven Platform and Azure Monitor.

Rate Limiting: A request restriction to prevent system overload. The default time in the Elven Platform is 5 minutes, but it can be adjusted as needed.