立即与支持人员聊天
与支持团队交流

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

Appendix G: Questions and answers about UC Analytics

Appendix G:
Questions and answers about UC Analytics
•
How often do the data collections actually gather data and when do they run?
•
When I view insights that show internal vs. external traffic, there is no data for internal traffic. Why?
•
Why are my OWA insights not showing any data?
•
Why did an insight show no data for a 30-day range though I initially set the data source to collect 30 days back?
•
If I collect both Exchange Tracking Logs and Exchange Mailbox Contents, are there duplicate items?
•
If I collect message data only from the Exchange tracking logs, is the message Send Date and delivery time available?
•
What are the differences between the Exchange Mailbox Contents and Exchange Tracking Logs data sources?
•
Why do I get an error when collecting Exchange configuration from multiple Exchange versions?
•
Why do I have to specify domain name when doing a multi-forest collection?
•
What insights are affected by the “Calculate insight data on server side” option?

Introduction

This section includes common questions and provides detailed answers to help you understand and troubleshoot your UC Analytics deployment.

How often do the data collections actually gather data and when do they run?

Does a data collection only collect data once per UTC day? When I set the frequency for how often a collection will run, does the counter start at midnight (UTC/local) or does it start when the Data Engine service starts?

Answer

By default, user-created data sources that collect a once-a-day snapshot of the data run aligned with UTC midnight and, when you enable the data source or start the Data Engine, at the interval specified in the data source. You can set a run interval for all data source jobs. The default interval is different for each data source, but all are more frequent than once a day.

The snapshot-type data sources, such as the Configuration data sources (Exchange/Lync/Cisco/Domain Controllers), only collect data once a day (first run in the UTC day). Even if you schedule the collections to run more than once a day, they take a “snapshot” of the data only once per UTC day. You might schedule the data sources to run multiple times per day to handle any situation when data collection fails.

For example, suppose you add an Exchange Configuration data source, schedule it to run every 6 hours, and you created the data source at 8:00 am UTC. The data source job will run (in UTC) as follows:

•
8:00 am (it runs when scheduled and collects data)
•
12:00 pm (this the next multiple of 6 hours after midnight – no data is collected because it is the second run of the day)
•
6:00 pm (no data collected)
•
12:00 am (collects data since first run of the day)
•
6:00 am (no data collected)

If an Exchange Configuration data source job is scheduled every 24 hours, and was created at 8:00 a.m. (UTC), then the data source will run (in UTC) as follows:

•
8:00 a.m.
•
12:00 a.m.
•
12:00 a.m.

If a data source job is still running during its next scheduled run time, the job run is skipped.

Some data sources (such as the Mailbox Contents data source) collect data continuously, only collecting data that is new or changed since the previous run. These data sources do not have a run interval time that is aligned on UTC midnight. The Mailbox Contents collection job runs continuously, with a minimum interval between the job run start times. The start time is unpredictable. If the job run takes less time than the minimum interval, the job will start X minutes (minimum interval) after the previous job run started. Otherwise, the job run starts immediately after the previous job completes.

For information about which data sources collect snapshot data and which data sources collect data continuously, see How often do collections update the data? .

As of release 8.5.1, you have the option to set a explicit schedule for a data source, specifying the time and day on which the data source collection job will run.

The main advantage of setting an explicit schedule for a data source collection is that it allows you to have jobs run separately over different time periods. For environments with a large number of configured data source collections, staggering the data source jobs can improve performance.

One difference between explicitly scheduled jobs and jobs using interval scheduling is that when the service restarts, jobs with an explicit schedule will not start immediately but will wait until the next scheduled time. Interval scheduled jobs will all run immediately after the service restarts.

If the real-time requirement for some data is not high, and the running of jobs together results in performance issues, you might set certain data source jobs to run once every two days.

When I view insights that show internal vs. external traffic, there is no data for internal traffic. Why?

When I view insights that show internal and external email traffic, such as the Mail Activity / Internal vs. External insight or Email - Activity, data is missing about internal traffic. I have configured the required data sources for the insights.

Answer

In addition to configuring the required data sources for each insight, you must also configure the Classifications | Domain Classifications in the Admin Settings to identify your internal domains. For information about configuring your internal domains, see Identifying your internal domains .

To see the required data sources for an insight, click INFO at the top of the insight.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级