-
Notifications
You must be signed in to change notification settings - Fork 42
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* costs * cloud fetcher * resource * costs * cost update * adding more steps * updating * updating tags text
- Loading branch information
1 parent
f027bca
commit e4f08bc
Showing
2 changed files
with
150 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,147 @@ | ||
| --- | ||
| layout: article | ||
| title: Configure Cloud Fetcher | ||
| image: https://dytvr9ot2sszz.cloudfront.net/logz-docs/social-assets/docs-social.jpg | ||
| description: Step by step guide to configuring Cloud Fetcher | ||
| permalink: /user-guide/cloud-fetcher.html | ||
| flags: | ||
| tags: | ||
| - cloud | ||
| - cloud fetcher | ||
| - ship data | ||
| - Azure | ||
| contributors: | ||
| - hidan | ||
| --- | ||
|
|
||
|
|
||
| Azure Cloud Fetcher offers a fast and efficient way to sync your Azure data with Logz.io, providing visibility and allowing you to monitor and troubleshoot your environments. With Azure Cloud Fetcher, you can monitor the performance and health of your systems in real-time, and quickly identify the root cause of issues and problems. | ||
|
|
||
| Azure may **charge additional fees** for using this integration. [Read more about Azure API costs](https://azure.microsoft.com/en-us/pricing/details/api-management/). | ||
| {:.info-box.important} | ||
|
|
||
| * [Set up Azure Cloud Fetcher](/user-guide/cloud-fetcher.html#set-up-azure-cloud-fetcher) | ||
| * [Set up Logz.io's Azure Cloud Fetcher](/user-guide/cloud-fetcher.html#set-up-logzios-azure-cloud-fetcher) | ||
|
|
||
| #### Set up Azure Cloud Fetcher | ||
|
|
||
| <div class="tasklist"> | ||
|
|
||
| ##### Create a new app in Azure | ||
|
|
||
| Enter your Azure portal and navigate to **App registrations > New registration**. | ||
|
|
||
| Give your app a name, choose Accounts in this organizational directory only (**Single tenant**), and click the Register button. | ||
|
|
||
|  | ||
|
|
||
| ##### Create a certificate | ||
|
|
||
| In your main app screen, click on **Add a certificate or secret**. | ||
|
|
||
|  | ||
|
|
||
| Next, create a **New client secret**. Give it a description and choose the expiration date, such as the 730 days option. Click **Add** to create the secret. | ||
|
|
||
| <!-- --> | ||
|
|
||
| Copy your secret's **Value** and save if for later use. This is needed to complete the setup process with Logz.io. | ||
|
|
||
| Client secret values **cannot be viewed except immediately after creation**. Be sure to save the secret when created before leaving the page. If you didn't keep the value, create a new client secret to continue the setup process. | ||
| {:.info-box.important} | ||
|
|
||
|  | ||
|
|
||
| ##### Assign a role | ||
|
|
||
| Navigate to **Subscriptions** and choose the relevant Azure subscription. Inside, click on **Access control (IAM) > Role assignments tab**. | ||
|
|
||
|  | ||
|
|
||
| Click on **Add** and choose **Add role assignment**. | ||
|
|
||
|  | ||
|
|
||
| Search for the **Monitoring reader** role, select it, and click next. | ||
|
|
||
|  | ||
|
|
||
| Ensure that the **User, group, or service principal** option is checked in the Members tab, and click on **+ Select members**. | ||
|
|
||
|  | ||
|
|
||
| Search for the name of the app you created and select it. Click **Review + assign** to confirm. Click on **Review + assign** again to apply the role. | ||
|
|
||
| ##### Send your details to Logz.io | ||
|
|
||
| To connect your Azure Cloud Fetcher with Logz.io you'll need to send the following information: | ||
|
|
||
| * **Client secret value** - that you created and copied in the [Create a certificate](/user-guide/cloud-fetcher.html#create-a-certificate) section. | ||
|
|
||
| Navigate to App registration and click on the app you created. There, you'll be able to find the following information: | ||
|
|
||
| * **Application (client) ID** | ||
| * **Directory (tenant) ID** | ||
|
|
||
|  | ||
|
|
||
| Next, navigate to Subscriptions and copy the **Subscription ID**: | ||
|
|
||
|  | ||
|
|
||
| And lastly, navigate to **Resource groups** and copy the group’s name associated with the app you created. _This step is optional._ | ||
|
|
||
|  | ||
|
|
||
|
|
||
| </div> | ||
|
|
||
| ## Set up Logz.io's Azure Cloud Fetcher | ||
|
|
||
| Once your Azure app is ready, navigate to Logz.io to continue the setup process. | ||
|
|
||
|
|
||
| <div class="tasklist"> | ||
|
|
||
| ##### Setup Azure Cloud Fetcher integration | ||
|
|
||
| Open **[Logz.io > Send data > Telemetry Collector](https://app.logz.io/#/dashboard/send-your-data/agent/new)** and Choose Azure. | ||
|
|
||
|  | ||
|
|
||
| ##### Enter your credentials | ||
|
|
||
| Take the credentials you've copied from your Azure app and enter the required values: | ||
|
|
||
| * **Tenant ID** - Your Azure app's directory ID | ||
| * **Client ID** - Your Azure app's application ID | ||
| * **Client Secret** - The value you've copied in the [Create a certificate](/user-guide/cloud-fetcher.html#create-a-certificate) section | ||
| * **Subscription** - Your Azure app's subscription ID | ||
| * *Optional* - **Resource group name** - The name of the group that's associated with the Azure app you created | ||
| * _Optional_ - **Tags** - You can add tags associated with the sent data for easier analysis and identification | ||
|
|
||
| Next, select the resource type you'd like to send. You can select **All services** to send all resource types of the project or manually add the relevant resources from the drop-down list. | ||
|
|
||
| Click **Next** to continue. | ||
|
|
||
|  | ||
|
|
||
| ##### Finish setting up your collector | ||
|
|
||
| Finilaze your collector by giving it a meaningful name, adding a description, and selecting which Metrics account you'd like to use. If you don't have an active Metrics account, it will be created automatically. | ||
|
|
||
| Click **Generate collector** to continue. | ||
|
|
||
| ##### Activate and run the collector | ||
|
|
||
| To get started with Azure Cloud Fetcher, toggle the **Enable Connection** on. You might have to wait a few minutes to see your data. | ||
|
|
||
|  | ||
|
|
||
| If you encounter an error and can't enable the connection, click **Advanced settings** to return to the configuration screen and verify the values you've entered are correct. | ||
|
|
||
| ##### Explore Logz.io | ||
|
|
||
| Once your Azure Cloud Fetcher is running, you can explore and analyze your data through Logz.io's dashboards. | ||
|
|
||
| </div> |