Chat now with support

Live-Hilfe anfordern
Registrierung abschließen

Anmelden

Preisinformationen anfragen

Vertrieb kontaktieren

Unified Communications Analytics 8.7 - Resource Kit

Inhaltsnavigation

Using the resource kit to extract data

Using the bulk data exporter

Why would the SendDate field be empty? Why would fields that link to Sender not be set?

Using Microsoft Power BI to explore the OData endpoint

Sample scenarios

Using Power BI Desktop to recreate a graph from the Email - Activity insight Using Power BI Desktop to create a graph for specific user email activity Using Power BI Desktop to create a bar chart for Exchange public folder item counts Using Power BI Desktop to create a trend for item counts in an Exchange public folder

About query performance

About columns with multiple values Limitations

Using the OData client library

About the sample files Overview: Using the OData library with PowerShell queries

Initializing the client library

Introducing the query structure Common query items

Finding a full attribute name About the Object item About the Time clause About the Where clause About more complex Where clauses About Metric values About the Group clause About the Trending clause Using the Select clause to return additional information Using the Order clause to define sorting

Working with the Query results

If you are running an Object query If you are running an Aggregate query

Notes about using theOData client library

Using the resource kit to extract data

UC Analytics provides a resource kit to give you easier access to the data you have collected. The resource kit includes the following tools:

•

A bulk data exporter that allows you to retrieve large amounts of data from UC Analytics. It allows you to export your collected data to a .csv file. The bulk data exporter is automatically installed with the UC Analytics Data Engine.

Using the bulk data exporter

•

An Open Data Protocol (OData) endpoint. You can access the OData endpoint using third party OData tools such as Microsoft Power BI or PowerView.

Using Microsoft Power BI to explore the OData endpoint

•

An OData client library. You can use the OData library to create ad hoc queries using PowerShell or C#.

Using the OData client library

Using the bulk data exporter

Using a command line interface, you can use the bulk exporter to extract specific data from your UC Analytics collected data. You run the bulk exporter on the directory that hosts the Data Engine.

To run the bulk exporter

1

Navigate to the Data Engine directory located in the UC Analytics installation directory on the server on which the Data Engine is installed.

2

Enter the executable name (UC.Analytics.Insights.DataEngine.BulkDataExport.exe) followed by the parameters that meet your inquiry.

Table 1. Parameters that can be used with the bulk exporter.
Available parameters	Definition
/FilePath	File path and file name of the output file
/ColumnDelimiter	Default character is , (comma). You can specify a different delimiter character (optional)
/Entity	Target entity name such as EmailMessage
/Fields	Comma separated field names such as SendDate or Sender.EmailAddress.Person.Name
/ObfuscatedFields	Comma separated field names (optional)
/Filter	Filter expression (optional)
/StartDate	Start date (optional)
/EndDate	End date (optional)
/PageSize	Buffer size (The default value is 1000)
/MaximumNumberOfResults	Number of objects (optional)
/OrderAscending	Sets the order of the results. True or false (default value is false)
/OrderByField	Field name (optional)
/ShowDataModel	Provides a complete up-to-date list of all the entities, fields, and their data types. Cannot be combined with other parameters

Listing all available entities and fields

To see a list of all the available entities, fields and their data types, use the /ShowDataModel switch on the command line and send the output to a file. For example, you could enter the following command:

D:\Program Files\Quest\UC Analytics\Data Engine> UC.Analytics.Insights.DataEngine.BulkDataExport.exe /ShowDataModel > dataModel.txt


	TIP: When you enter parameters, remember that field names are case-sensitive and must exactly match the names as shown by the /ShowDataModel switch.

Common entities in the UC Analytics data model

The following is a list of common entities that comprise the UC Analytics data model:

•

•

ActiveDirectoryObjectSnapshot

•

•

LyncPeerToPeerSession

•

•

CiscoConference

•

CiscoPeerToPeerSession

Additionally, you can retrieve the full metadata from OData (http://<server name>:1336/$metadata).

The resource kit supports obfuscated data so that you can do data analysis without revealing private data.Data obfuscation is a form of data masking where data is purposely scrambled to prevent unauthorized access to sensitive materials.

Examples of bulk exporter commands

Your query can be simple or complex, depending on the depth of data that you want to extract.

In a simple example, you can extract the subject, send date, and sender name for all the email message in your database:

UC.Analytics.Insights.DataEngine.BulkDataExport.exe /Entity EmailMessage /FilePath output.csv /Fields "Subject, SendDate, Sender.EmailAddress.Person.Name"

In a more complex example, you could filter the query to include only the subject lines from email messages that were sent by Stuart Murgal as of January 1, 2015.

UC.Analytics.Insights.DataEngine.BulkDataExport.exe /Entity EmailMessage /FilePath output.csv /Filter "Sender.EmailAddress.Person.Name == \"Stuart Mughal\" "/Fields "Subject" /StartDate "2015-01-01"

Examples using multiple filters

In another situation, you might want to filter for multiple users in a single query. In this example, you could export the message subject lines for messages sent on a specific date by several specified senders and also see the recipients (To, CC, and BCC) for each message. In this example, the || (double pipe) means OR.

UC.Analytics.Insights.DataEngine.BulkDataExport.exe /Entity EmailMessage /FilePath C:\output.csv /Fields "Subject, SendDate, Sender.EmailAddress.Person.Name,RecipientsInTo.EmailAddress.Person.Name,RecipientsInCc.EmailAddress.Person.Name,RecipientsInBcc.EmailAddress.Person.Name"," Recipients.EmailAddress.Person.Name" /Filter "Sender.EmailAddress.Person.Name == \"Salvatore Denham\" || Sender.EmailAddress.Person.Name == \"Tony Brownlee\" || Sender.EmailAddress.Person.Name == \"Maria Santos\" || Sender.EmailAddress.Person.Name == \"Eric Johnson\" || Sender.EmailAddress.Person.Name == \"Frederick Johansson\" || Sender.EmailAddress.Person.Name == \"Sandra Butterfield\" || Sender.EmailAddress.Person.Name == \"Vladimir Ivanov\" || Sender.EmailAddress.Person.Name == \"Caroline Northwood\" || Sender.EmailAddress.Person.Name == \"Andrew Chen\"" /StartDate "2018-10-09" /EndDate "2018-10-10"

In the following example, the query is filtering message recipients (To, CC, and BCC) in a specific department (R&D-Development) who received messages from senders in a specific company (Sitraka) and office. The query defines a specific date and includes the message subject line. In this example, the && (double ampersand) means AND.

UC.Analytics.Insights.DataEngine.BulkDataExport.exe /Entity EmailMessage /FilePath C:\output.csv /Fields "Subject, SendDate, Sender.EmailAddress.Person.Name,RecipientsInTo.EmailAddress.Person.Name,RecipientsInCc.EmailAddress.Person.Name,RecipientsInBcc.EmailAddress.Person.Name"," Recipients.EmailAddress.Person.Name" /Filter "Recipients.EmailAddress.Person.Department == \"R&D-Development\" && Sender.EmailAddress.Person.Company == \"Sitraka\" && Sender.EmailAddress.Person.Office==\"AMER-US-Aliso Viejo\"" /StartDate "2018-10-09" /EndDate "2018-10-11"

Suppose that you want to refine your query to view the recipients (To, CC, and BCC) of all messages sent on a specific day from two specific senders in a company. In this example, the query is retrieving messages sent by Anthony Jones or Maria Santos at Sitraka to recipients in your R&D-Development department. This example uses both OR (||) and AND (&&).

UC.Analytics.Insights.DataEngine.BulkDataExport.exe /Entity EmailMessage /FilePath C:\output.csv /Fields "Subject, SendDate, Sender.EmailAddress.Person.Name,RecipientsInTo.EmailAddress.Person.Name,RecipientsInCc.EmailAddress.Person.Name,RecipientsInBcc.EmailAddress.Person.Name"," Recipients.EmailAddress.Person.Name" /Filter "(Recipients.EmailAddress.Person.Department == \"R&D-Development\" || Sender.EmailAddress.Person.Company == \"Sitraka\")&& (Sender.EmailAddress.Person.Name ==\"Anthony Jones\"|| Sender.EmailAddress.Person.Name==\"Maria Santos\")" /StartDate "2018-10-09" /EndDate "2018-10-11"

Why would the SendDate field be empty?

Why would some fields such as SendDate be empty?

The Send Date is affected by the types of data collections you have scheduled, the sources from which you are collecting, and by the message origins. If you only collect from the Exchange Tracking Logs data source, but do not collect from mailboxes using the Exchange Mailbox Contents data source, the Send Date may be approximate or missing for some messages. For example, the SendDate may not be set if you are not collecting all the tracking logs from all your Exchange mailbox and hub servers.

If you collect from both the Exchange Mailbox Contents and the Exchange Tracking Logs data sources, the Send Date is always set by the Mailbox Contents data collection. To always collect the exact Send Date, you must collect using both the Tracking Logs and the Mailbox Contents data sources.

When Send Date is approximate

If you collect only from the Exchange Tracking Logs data source, the Send Date for SMTP or inbound messages is approximate. For messages submitted through SMTP or originating from outside your Exchange organization, the Delivery Time is not calculated until the Exchange Calculation job has run.

For multi-hop message delivery, a message might appear in the tracking logs on several Exchange servers. Since the Send Date will be set by an event (StoreDriver Submit or SMTP Receive) which can appear in any one of the tracking logs, the Send Date is approximate.

Why would fields that link to Sender not be set?

Sometimes Sender and fields that follow links such as Sender.DeliveryTime are not set. Why?

The SenderDeliveryTime field is set only if senders send the message to themselves. The RecipientsDeliveryTime field is usually set.

The SenderFirstResponseTime is the duration between the receipt of the message, and the first reply to the message. So the field is mainly applicable to Recipients (rather than Sender) and is set only for messages that are collected from mailboxes using the Mailbox Contents data source (not Exchange Tracking Logs).

The SenderSendTimeofDay and SentAfterHours fields are also set only for messages collected using the Mailbox Contents data source.

If you want the sender name rather than the key, you can use Sender.EmailAddress.DisplayName field instead.

Self-Service-Tools: Knowledge Base; Benachrichtigungen und Warnmeldungen; Produkt-Support; Software-Downloads; Technische Dokumentationen; Benutzerforen; Videoanleitungen; RSS Feed

Kontakt: Unterstützung bei der Lizenzierung; Technische Support; Alle anzeigen

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen

© ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center