While developing an application, you often want to what's being written to the logs in near-real time when running in Azure.

There are two ways to view a stream of log files being generated by your function executions.

* **Built-in log streaming**: the App Service platform lets you view a stream of your application log files. This is equivalent to the output seen when you debug your functions during [local development](functions-develop-local.md) and when you use the **Test** tab in the portal. All log-based information is displayed. For more information, see [How to stream logs](../app-service/troubleshoot-diagnostic-logs.md#streamlogs). This streaming method supports only a single instance, and can't be used with an app running on Linux in a Consumption plan.

* **Live Metrics Stream**: when your function app is [connected to Application Insights](#enable-application-insights-integration), you can view log data and other metrics in near-real time in the Azure portal using [Live Metrics Stream](../azure-monitor/app/live-stream.md). Use this method when monitoring functions running on multiple-instances or on Linux in a Consumption plan. This method uses [sampled data](#configure-sampling).

Log streams can be viewed both in the portal and in most local development environments.

You can view both types of log streams in the portal.

#### Built-in log streaming

#### Live Metrics Stream

To view the Live Metrics Stream for your app, select the **Overview** tab of your function app. When you have Application Insights enables, you see an **Application Insights** link under **Configured features**. This link takes you to the Application Insights page for your app.

In Application Insights, select **Live Metrics Stream**. [Sampled log entries](#configure-sampling) are displayed under **Sample Telemetry**.


### Core Tools

[!INCLUDE [functions-streaming-logs-core-tools](../../includes/functions-streaming-logs-core-tools.md)]

The recommended way to monitor the execution of your functions is by integrating with Azure Application Insights. You can also stream execution logs to your local computer. To learn more, see [Monitor Azure Functions](functions-monitoring.md).

When you create a function app in the Azure portal, the Application Insights integration is done for you by default. However, when you create your function app by using the Azure CLI, the integration in your function app in Azure isn't done.

* [Customizing person models overview](customize-person-model-overview.md)

* [Customizing person models using the Video Indexer website](customize-person-model-with-website.md)

* [Customizing person models using the Video Indexer API](customize-person-model-with-api.md)

[Video Indexer overview](video-indexer-overview.md)

title: Customize networking configurations for failover VM | Microsoft Docs

description: Provides an overview of customize networking configurations for failover VM in the replication of Azure VMs using Azure Site Recovery.

services: site-recovery

author: rajani-janaki-ram

manager: rochakm

ms.service: site-recovery

ms.topic: article

ms.date: 08/07/2019

ms.author: rajanaki

This article provides guidance on customizing networking configurations on the target Azure VM when you're replicating and recovering Azure VMs from one region to another, using [Azure Site Recovery](site-recovery-overview.md).

Learn how Site Recovery provides disaster recovery for [this scenario](azure-to-azure-architecture.md).

The following key resource configurations can be provided for the failover VM while replicating Azure VMs.

- [Internal Load Balancer](https://docs.microsoft.com/azure/load-balancer/load-balancer-standard-overview#what-is-standard-load-balancer)

- [Public IP](https://docs.microsoft.com/azure/virtual-network/virtual-network-ip-addresses-overview-arm#public-ip-addresses)

- [Network Security Group](https://docs.microsoft.com/azure/virtual-network/manage-network-security-group) both for the subnet and for the NIC

- Ensure that you plan your recovery side configurations in advance.

- You need to create the networking resources in advance. Provide it as an input so that Azure Site Recovery service can honor these settings and ensure that the failover VM adheres to these settings.

1. Navigate to **Replicated Items**.

2. Click on the desired Azure VM.

3. Click on **Compute and Network**, and **Edit**. You will notice that the NIC configuration settings include the corresponding resources at the source.


4. Click **Edit** near the NIC you want to configure. In the next blade that opens up, select the corresponding pre-created resources in the target.


5. Click **OK**.

Site Recovery will now honor these settings and ensure that the VM on failover is connected to the selected resource via the corresponding NIC.

If you are unable to select or view a networking resource, please go through the following checks & conditions:

- The target field for a networking resource is only enabled if the source VM had a corresponding input. This is based on the principle that for a disaster recovery scenario, you would want either the exact or a scaled down version of your source.

- For each of the networking resources in question some filters are applied in the dropdown to ensure that the failover VM can attach itself to the resource selected and the failover reliability is maintained. These filters are based on the same networking conditions that would have been verified when you configured the source VM.

Internal load balancer validations:

1. Subscription and Region of LB and the target VM should be the same.

2. The virtual network associated with the Internal Load Balancer and that of the target VMshould be the same.

3. The target VM’s Public IP SKU and the Internal Loadbalancer's SKU should be the same.

4. If the target VM is configured to be placed in an availability zone, then check if the load balancer is zone redundant or part of any availability zone. (Basic SKU Load Balancers do not support zones and will not be shown in the drop-down in this case.)

5. Ensure that the Internal LoadBalancer has a pre-created backend pool and front-end configuration.

Public IP address:

1. Subscription and Region of Public IP and the target VM should be the same.

2. The target VM’s Public IP SKU and the Internal Loadbalancer's SKU should be the same.

Network security group:

1. Subscription and Region of Network security group and the target VM should be the same.

- name: Customize networking configurations of the target Azure VM

href: azure-to-azure-customize-networking.md

"articles/azure-databricks/**/*.md": ["Azure","Azure Databricks"],

"articles/cosmos-db/**/*.md": ["Azure","Azure Cosmos DB"],

"articles/data-catalog/**/*.md": ["Azure","Azure Data Catalog"],

"articles/data-explorer/**/*.md": ["Azure","Kusto","Azure Data Explorer"],

"articles/data-lake-analytics/**/*.md": ["Azure","Azure Data Lake Analytics"],

"articles/data-share/**/*.md": ["Azure","Azure Data Share"],

"articles/mariadb/**.md": ["Azure","Azure Database for MariaDB"],

"articles/mysql/**.md": ["Azure","Azure Database for MySQL"],

"articles/postgresql/**.md": ["Azure","Azure Database for PostgreSQL"],

"articles/stream-analytics/**/*.md": ["Azure","Stream Analytics"]

| Maximum telemetry item size | 64,000 kB |

| Maximum telemetry items in a batch | 64 K |

author: ggailey777

ms.author: glenga

ms.date: 7/24/2019

ms.topic: include

ms.service: azure-functions

Use the `logstream` option to start receiving streaming logs of a specific function app running in Azure, as in the following example:

func azure functionapp logstream <FunctionAppName>

You can also view the [Live Metrics Stream](../articles/azure-monitor/app/live-stream.md) for your function app in a new browser window by including the `--browser` option, as in the following example:

func azure functionapp logstream <FunctionAppName> --browser