![Macrovision Corporation SAMREPORT-LITE 2006 Manual Download Page 25](http://html1.mh-extra.com/html/macrovision-corporation/samreport-lite-2006/samreport-lite-2006_manual_3269583025.webp)
Data Filters
Some of the information contained in the report log is subject to filtering.
Two filters can be specified for a Usage Summary report—feature and user.
Multiple filter categories for one report are applied with a Boolean AND
operation—all the specified conditions must be satisfied. If a report is filtered
on user==User1 and feature==Feature2, the resulting report contains usage of
Feature2 by User1.
Multiple instances of a single filter category are applied with a Boolean OR
operation. If a report is filtered on user==User1 and user==User2, the resulting
report contains usage of features by either User1 or User2.
Multiple filter values for the same filter category can be specified on the same
line separated by a space or on separate lines. For example, user==User1 User2
is equivalent to user==User1 and user==User2.
Reports and Time Zones
Timestamps in a report log are determined by the clock on the license server
machine. The times are converted from the time zone of the license server
machine and stored in the report log in Greenwich Mean Time (GMT), also
known as Universal Time (UTC). Therefore, the data in a report log is
insensitive to time zones, and you can run a report using report logs that were
written on machines in different time zones without compensating for time
differences. Reports, on the other hand, show time using the time zone set
on the machine where the report was generated. SAMreport-Lite translates
times in UTC from the report log using the offset for the time zone of the
machine on which SAMreport-Lite is running.
For example, if you have an event in a report log that was written at 1pm by
a vendor daemon running on a license server in the US Eastern time zone, its
timestamp in the report log would be written as 6pm GMT. If an event in a
report log was written at 10am by a vendor daemon running on a license
server in the US Pacific time zone, its timestamp would also be written as 6pm
GMT. If those two report logs were used to generate a report in the US Pacific
time zone, those two events would both be reported at 10am. If the same
report were generated on a computer in the US Eastern time zone, the events
would both be reported at 1pm.
Possible causes for the times in reports that are different than you expect are:
■
The time zone on the license server machine is set incorrectly. If the time
zone is not set correctly, and the system clock has been set to show local
Data Filters | 21