Azure Logz Monitor

This page shows how to write Terraform for Logz Monitor and write them securely.

azurerm_logz_monitor (Terraform)

The Monitor in Logz can be configured in Terraform with the resource name azurerm_logz_monitor. The following sections describe how to use the resource and its parameters.

Example Usage from GitHub

An example could not be found in GitHub.

Review your Terraform file for Azure best practices

Shisho Cloud, our free checker to make sure your Terraform configuration follows best practices, is available (beta).

Parameters

The following arguments are supported:

  • name - (Required) The name which should be used for this logz Monitor. Changing this forces a new logz Monitor to be created.

  • resource_group_name - (Required) The name of the Resource Group where the logz Monitor should exist. Changing this forces a new logz Monitor to be created.

  • location - (Required) The Azure Region where the logz Monitor should exist. Changing this forces a new logz Monitor to be created.

  • plan - (Required) A plan block as defined below.

  • user - (Required) A user block as defined below.


  • company_name - (Optional) Name of the Logz organization. Changing this forces a new logz Monitor to be created.

  • enterprise_app_id - (Optional) The ID of the Enterprise App. Changing this forces a new logz Monitor to be created.

NOTE Please follow Set up Logz.io single sign-on to create the ID of the Enterprise App.

  • enabled - (Optional) Whether the resource monitoring is enabled?

  • tags - (Optional) A mapping of tags which should be assigned to the logz Monitor.


An plan block exports the following:

  • billing_cycle - (Required) Different billing cycles. Possible values are MONTHLY or WEEKLY. Changing this forces a new logz Monitor to be created.

  • effective_date - (Required) Date when plan was applied. Changing this forces a new logz Monitor to be created.

  • plan_id - (Required) Plan id as published by Logz. Possible values are 100gb14days. Changing this forces a new logz Monitor to be created.

  • usage_type - (Required) Different usage types. Possible values are PAYG or COMMITTED. Changing this forces a new logz Monitor to be created.


An user block exports the following:

  • email - (Required) Email of the user used by Logz for contacting them if needed. Changing this forces a new logz Monitor to be created.

NOTE If you use the Azure CLI to authenticate to Azure, the Email of your Azure account needs to be granted the admin permission in your Logz.io account. Otherwise, you may not be able to delete this resource. There is no such limitation for the Service Principal authentication.

  • first_name - (Required) First Name of the user. Changing this forces a new logz Monitor to be created.

  • last_name - (Required) Last Name of the user. Changing this forces a new logz Monitor to be created.

  • phone_number - (Required) Phone number of the user used by Logz for contacting them if needed. Changing this forces a new logz Monitor to be created.

In addition to the Arguments listed above - the following Attributes are exported:

  • id - The ID of the logz Monitor.

  • single_sign_on_url - The single sign on url associated with the logz organization of this logz Monitor.

  • logz_organization_id - The ID associated with the logz organization of this logz Monitor.

Explanation in Terraform Registry

Manages a logz Monitor.

Azure Resource Manager Example

Azure Resource Manager code does not have the related resource.

Frequently asked questions

What is Azure Logz Monitor?

Azure Logz Monitor is a resource for Logz of Microsoft Azure. Settings can be wrote in Terraform.

security-icon

Automate config file reviews on your commits

Fix issues in your infrastructure as code with auto-generated patches.