Chatee ahora con Soporte
Chat con el soporte

Unified Communications Analytics 8.8.3 - Deployment Guide

Prerequisites for your installation Installing UC Analytics Configuring UC Analytics Adding data sources for Active Directory or Azure Active Directory Adding data sources, chargeback costs, and thresholds for Exchange and Exchange Online
Permissions needed to collect Exchange on-premises or hybrid data Permissions needed to collect from native Exchange Online Creating an Exchange Configuration data source Creating an Exchange Tracking Logs data source Creating an Exchange Mailbox Contents data source Do I need both Exchange Tracking Logs and Exchange Mailbox Contents collections? Creating an Exchange IIS Logs data source Creating an Exchange Mailbox Content Summary data source Creating an Exchange Calendar data source Creating an Exchange Public Folders data source Adding Exchange Online hybrid data sources for hybrid Office 365 Adding Exchange Online data sources for native Office 365 Setting chargeback costs for Exchange Setting thresholds for Exchange metrics Omitting words when filtering by subject or body
Adding data sources, chargeback costs, and thresholds for Skype for Business/Lync Adding data sources, chargeback, and thresholds for Cisco Managing which insights can seen by users Configuring and managing subscriptions Making changes to your deployment Appendix A:Configuring Exchange and Office 365 Appendix B:Configuring the Skype for Business or Lync Server Appendix C:Configuring IIS Log Files to capture ActiveSync or OWA events Appendix D:PowerShell cmdlets used by data sources Appendix E:Backup and recovery options Appendix F:Custom configurations Appendix G: Questions and answers about UC Analytics

Modifying collection days for data collections from log files

In some circumstances, you might create a new data source to collect from log files (IIS logs, Exchange tracking logs, Skype for Business/Lync CDR and QOE logs) that have already been collected. If you have a large retention period, such as 365 days, you might want to limit the amount of data that the new data source collects.

In this case, you can set a configuration option to restrict the initial collection time period for the specific data sources that collect from log files (Exchange Tracking Logs, IIS Logs, Skype for Business / Lync CDR Database, and Skype for Business / Lync QoE Database). You set the configuration option in the UC.Analytics.Insights.DataEngine.DataCollector.dll.config file.

You can modify the collection days for the Skype for Business / Lync CDR Database and Skype for Business / Lync QoE Database data sources.

When the collection job enumerates the files within the tracking log or IIS log folders, it retrieves the file date from the log file name (such as MSGTRK2019070413-1.LOG). The job compares the file date with the following job values:

If the file date is newer than both the retention date and start of job date, the collection job continues to process the log file. Otherwise, the log file is skipped. If detailed logging is enabled, the following message is logged in the Data Engine service logs: "Skip tracking log file {0}, because it is too old". Also, if the log entry (date-time) is too old, the collection job skips it.

Changing initial collection days for Exchange (Online) Mailbox Contents data sources

By default, both an initial Exchange Mailbox Contents data collection and an initial Exchange Online Mailbox Contents data collection gather messages for the past 30 days in the target mailboxes.

If the you want to gather older messages in the initial collection, you must update the initialDataCollectionDays setting in sections of the UC.Analytics.Insights.DataEngine.DataCollector.dll.config file and restart Data Engine service. You update the initialDataCollectionDays setting before you create the data sources.

Changing default values for formatted .csv or .tsv file exports

When exporting an insight or creating a subscription, in addition to PDF and MHTML output, you can select one several.csv or .tsv file formats:

By default, the formatted outputs include information such as the insight title, header details such as the insight description, the user who generated the file, date range, filters that were applied to the insight, and date of the export. The formatted output also includes any customized units that were specified in the insight, such as MB instead of KB.

In special cases, you might want to export an insight to formatted .csv or .tsv output but without the title, header information, or custom units.

You can modify the formatted .csv or .tsv file output by editing parameters in the UC.Analytics.Insights.DataEngine.InsightLogic.dll.config file.

Excluding insight date range and filters from subscription emails

By default, for a subscription that is sent by email, the email subject contains the insight date range and the body contains both the insight date range and filters that were selected.

In some cases, you might not want this information to be included in the email. You can exclude this information from the email by editing parameters in the UC.Analytics.Insights.DataEngine.InsightLogic.dll.config file.

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación