| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Purpose
The Microsoft Azure collector gets data from Azure cloud computing services. Common uses are:
...
Features | Details |
|---|---|
Allow parallel downloading ( | The vm_metrics service cannot work in multipod mode. If you want to use the event_hubs service in multipod mode, you must not include a vm_service in the same collector. |
Running environments |
|
Populated Devo events |
|
Flattening pre-processing |
|
Allowed source events obfuscation |
|
Data source description
...
Data source
...
Description
...
API endpoint
...
Collector service name
...
Devo table
...
VM Metrics
...
With the advantages of the Microsoft Azure API, one can obtain metrics about the deployed Virtual Machines, gathering them on our platform, making it easier to query and analyze in the Devo platform and Activeboards.
...
Azure Compute Management Client SDK and Azure Monitor Management Client SDK
...
vm_metrics
...
cloud.azure.vm.metrics_simple
...
Event Hubs
...
Several Microsoft Azure services can generate some type of execution information to be sent to an EventHub service. (see next section)
...
Azure Event Hubs SDK
...
event_hubs and event_hubs_autodiscover
...
<auto_tag_description>
| Info |
|---|
Valid for all cloud.azure tables by setting the output option to stream to Event Hub. |
Event hubs: Auto-categorization of Microsoft Azure service messages
Many of the available Microsoft Azure services can generate some type of execution information to be sent to an EventHub service. This type of data can be categorized as events or metrics. The events, in turn, can be from different subtypes: audits, status, logs, etc.
All such data will be gathered by Devo’s Microsoft Azure collector and sent to our platform, where message auto-categorization functionality is enabled for sending the messages to relevant Devo tables in an automatic way.
Although EventHub is the service used for centralizing Azure services' data, it also generates information that can be sent to itself. Learn more in this article.
| Note |
|---|
In case the amount of egress data exceeds Throughput per Unit limits set by Azure (2 MB/s or 4096 events per second), it won’t be possible for Devo to continue reliable ingestion of data. You can monitor ingress/egress throughput in Azure Portal EventHub Namespace, and based on trends/alerts, you can add another EventHub to resolve this. To avoid this from happening in the first place, please follow scalability guidance provided by Microsoft in their technical documentation. |
Vendor setup
The Microsoft Azure collector centralizes the data with an Event Hub using the Azure SDK. To use it, you need to configure the resources in the Azure Portal and set the right permissions to access the information.
Event Hub events
Event Hub Auto-Discover
| Expand | ||
|---|---|---|
| ||
About the featureTo configure access to event hubs for the auto-discovery feature, you need to grant the necessary permissions to the registered application to access the Event Hub without using the Role assignment (Namespace)Repeat the steps from the Event Hubs Role Assignment section, except that the necessary role is the Azure Event Hubs Namespace Data Owner role. This allows the collector to enumerate the event hubs in the namespace and create consumer groups if necessary. |
Minimum configuration for basic pulling
Although this collector supports advanced configuration, the fields required to retrieve data with basic configuration are defined below.
| Info |
|---|
This minimum configuration refers exclusively to those specific parameters of this integration. There are more required parameters related to the generic behavior of the collector. Check setting sections for details. |
...
Setting
...
Details
...
tenant_id
...
The Azure application tenant ID.
...
client_id
...
The Azure application client ID.
...
client_secret
...
The Azure application client secret.
...
subscription_id
...
The Azure application subscription ID.
| Info |
|---|
For Azure Event Hub, it is enough with the event hub name and the connection string (and optionally consumer group). No credentials are required. |
Accepted authentication methods
...
Authentication method
...
Tenant ID
...
Client ID
...
Client secret
...
Subscription ID
...
OAuth2
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||||
|---|---|---|---|---|
|
...
| Status | ||||
|---|---|---|---|---|
|
Run the collector
...
Collector services detail
...