Telemetry In Fabric

[vi1996ash]

Question 1: What is difference between configuring telemetry in azure log analystics vs KQL monitor database?

Azure Log analytics

Kql Monitoring

Question 2: How can we get fabric data pipeline monitoring logs? If we need admin access then for microsoft tenant where can we request it?

[vi1996ash]

Hi @v-cboorla-msft , This is very generic answers. I was looking in terms of details. For example in KQL monitoring i see 4 more tables. While in Log analytics we only see PowerBIDatasetsWorkspace. What is the refresh time of both.

[vi1996ash]

@v-cboorla-msft Any update on above query

[v-cboorla-msft]

Hi @vi1996ash 

Apologies for the delay in response.

In Azure Log Analytics, you can configure telemetry data collection by enabling data sources and defining what data to collect. The collected data is stored in a Log Analytics workspace, and you can use KQL to query and analyze the data. In the context of Microsoft Fabric, the telemetry data is stored in a table called PowerBIDatasetsWorkspace. On the other hand, KQL monitoring provides more detailed and granular data about the Fabric environment.

The refresh time for Azure Log Analytics and KQL monitoring can vary depending on the configuration and the volume of data being ingested. For Azure Log Analytics, the refresh time is typically around 1-2 minutes, depending on the data source and the frequency of data collection. You can configure the refresh time by setting the refresh_interval parameter in the Log Analytics workspace. For KQL monitoring, the refresh time is typically around 1-5 minutes, depending on the table and the frequency of data ingestion.

Please note that these refresh times are approximate and may vary depending on the specific configuration and usage of your Microsoft Fabric environment.

I hope this information helps.

Thank you.

[v-cboorla-msft]

Hi @vi1996ash 

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others .
If you have any question relating to the current thread, please do let us know and we will try out best to help you.
In case if you have any other question on a different issue, we request you to open a new thread.

Thank you.

[v-cboorla-msft]

Hi @vi1996ash 

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. If you have any question relating to the current thread, please do let us know and we will try out best to help you. In case if you have any other question on a different issue, we request you to open a new thread.

Thank you.

[v-cboorla-msft]

Hi @vi1996ash 

Thanks for using Microsoft Fabric Community.

In the context of Microsoft Fabric, here are the differences between configuring telemetry using Azure Log Analytics and Kusto Query Language (KQL) for monitoring databases:

Azure Log Analytics:

Primarily serves as a centralized repository for log data storage and analysis for various sources within a Microsoft Fabric environment. This is a service within Azure Monitor that provides a workspace for collecting and analyzing logs and telemetry data from various sources, including Azure resources, applications, and on-premises systems. You configure telemetry data collection by enabling data sources and defining what data to collect. Azure Log Analytics uses KQL (Kusto Query Language) for querying and analyzing the collected data.

For more details please refer : Using Azure Log Analytics in Power BI - Power BI | Microsoft Learn

Kusto Query Language (KQL) database:

KQL acts as the primary query language for analyzing data stored within Fabric Monitor Logs. There isn't a specific concept of a "KQL monitor database" within Azure Monitor. KQL is the language used to query data stored in Azure Monitor Logs, which includes data collected through Azure Log Analytics workspaces. You don't configure telemetry in a KQL database, but you would use KQL queries to analyze the telemetry data stored in Azure Monitor Logs. To help you monitor workspace activity, Microsoft will create a read-only KQL database to store data collected in logs and then automatically turn on logging. You can pause logging whenever you need to.

For more details please refer : Kusto Query Language (KQL) Databases in Microsoft Fabric

To monitor your data pipeline runs in Microsoft Fabric, follow these steps:

Hover over your pipeline in your workspace. This will bring up three dots to the right of your pipeline name. Select the three dots to find a list of options. Then, choose View run history. This action opens a fly-out on the right side of your screen with all your recent runs and run statuses.

Please refer the documentation for more details : How to monitor pipeline runs - Microsoft Fabric | Microsoft Learn

For admin access please refer : Enable Microsoft Fabric for your organization - Microsoft Fabric | Microsoft Learn

I hope this information helps. Please do let us know if you have any further queries.

Thank you.

[v-cboorla-msft]

Hi @vi1996ash 

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet.
In case if you have any resolution please do share that same with the community as it can be helpful to others.
Otherwise, will respond back with the more details and we will try to help.

Thank you.