IT Asset Management (Cloud)
The
Upload Status tab helps to identify any issues with the upload of
files from this
inventory beacon to the central
application server, and displays
time stamps for the following:
In larger, multi-server implementations:
- Some of these import types go to the inventory server, such as FlexNet inventory files
and usage tracking files. These require a second stage of import from the inventory
database to the compliance database, which is normally scheduled overnight. This
typically means that the results of these imports are normally available on a "next day"
basis, after the overnight import and license compliance calculations.
- Other import types are routed directly into the compliance database, meaning that the results may be
available in the web interface on the same day, shortly after a file is
uploaded.
These differences may mean that some import types fail while others succeed, if there
happen to be problems connecting to one of the FlexNet databases but not another.
In addition to the
Inventory beacon upload status grid, a series of
bar charts are displayed. The
Beacon statistic (last 7 days) bar chart
shows the total number of files received and uploaded over the span of the last seven days.
The other bar charts are specific to a particular file type showing the number of files
received and uploaded each day, over the span of the last seven days for that specific file
type. The
Last known received and
Last known
uploaded metrics specified under each chart are the same as described above but
correspond to that particular file type (applies to all file types for the
Beacon
statistic (last 7 days) bar chart).
Note: Last known received and last known
uploaded bar chart date and time stamps are in UTC time.
The following columns (listed alphabetically) are available on this tab:
Property |
Description |
Files received (last 24 hours) |
The number of inventory/usage files received by the inventory beacon in the
last 24 hours.
|
Files to upload |
The count of files for each type of import that are on this inventory beacon
and awaiting upload to the application server. A count of zero is a good
thing, meaning that all files (for the import type) have been successfully uploaded.
|
Files uploaded (last 24 hours) |
The number of inventory/usage files uploaded from the inventory beacon in the
last 24 hours.
|
Import type |
The distinct kinds of imports that may have file uploads blocked for some reason.
Note that an individual import type may combine more than one file type.
These names reflect the names of folders on your inventory beacons, under
ProgramData\Flexera Software\Incoming. Standard values include:
- ActiveDirectory — Data extracted from Microsoft
Active Directory domains, for upload to the inventory database (see Active Directory Tab).
- ActivityStatus — Details about system tasks
involving inventory beacon activity, such as progress on third-party or
FlexNet inventory gathering (including error reporting), policy updates, and the
like. Uploaded to the compliance database. Results are displayed on the
System Tasks page in the web interface (see
System Tasks).
- BeaconStatus — Details on normal inventory beacon operations (such as policy updates, connectivity, and reporting
status), but not including inventory details. Uploaded to the compliance database. Results are displayed on the
Beacons page in the web interface (see Beacons).
- ClientAccess — Files (.swcc)
tracking access for consumption on Microsoft Client Access Licenses (CALs). Data
is uploaded to the inventory database, and results are visible pages like
Unlicensed CAL Usage and All Licenses
(see Unlicensed CAL Usage, for example).
- Discovery — Results of network discovery by
inventory beacons, saved in .disco files for upload
to the compliance database. May include additional
.disco files created by FlexNet Inventory Agent, locally
installed on target inventory devices where it has 'uncovered' Oracle databases.
Discovery files are included in the overnight upload that can help recover from
temporary networking issues. These map to pages like All Discovered Devices in the web interface.
- Inventories — These include FlexNet inventory
(.ndi files) destined for the inventory database (see, for
example, help for the All Inventory page).
- Logs — Log files for inventory beacon
activity are saved here, and as a convenience uploaded to the application server. From the General tab of the
inventory beacon properties, you can click View activity
log to navigate to the Activity Log page (see
Activity Log). This combines information
from inventory beacons with other activity logs, but accessing through this
path automatically filters the listing to show results for just the one inventory beacon.
- RemoteApplication — A staging folder for software
inventory from Citrix Virtual Apps, which is to be uploaded to the inventory
database. Depending on the type of virtualized applications being served, the
evidence appears in the web interface in either the installer evidence
list (for App-V or streaming profile applications delivered through Citrix Virtual
Apps), or in the file evidence list (for file-based applications managed through Citrix Virtual Apps). For details, see All Evidence.
- UsageData — Records of application usage sometimes
used for calculating consumption on user-based licenses. This is uploaded through
the inventory database. The number of inventory devices reporting usage of each
application is listed in the All Applications page.
- VdiAccess — Files (.vdi)
tracking users or inventory devices that access virtual desktops. VMware, Citrix,
and Microsoft each support their own virtual desktop infrastructure platforms. For
example, for more information, see the XenApp Server Adapter chapter in the
IT Asset Management Inventory Adapters and Connectors Reference PDF, available at https://docs.flexera.com/.
|
Newest pending |
The time since the most recent file (of each import type) was added to the queue for
uploading. The possible values (both for newest and oldest) include:
- Blank when there are no files blocked for the current import type.
- Less than 30 mins (minutes) — A minor delay may
self-correct with the upload that (by default) is scheduled overnight for each
inventory beacon.
- 30-60 mins — May also self-correct overnight. Even
if you are using IT Asset Management for 30-minute inventories of servers for
subcapacity IBM PVU licensing, this delay is not critical, since the inventory beacon simply queues all the incoming inventory files and uploads them
when possible, such as the next overnight catch-up. (However, if the
locally-installed FlexNet Inventory Agent cannot upload to the inventory beacon, that is quite serious, since the local files on the
inventory device are overwritten every 30 minutes.)
- N hours — The period is rounded
up to the nearest hour.
- N day(s) or
week(s) or month(s) —
This scale of delay (rounded up) in uploading indicates a problem that you should
investigate and fix. Any period that passes the overnight catch-up means that
uploads are consistently failing for some reason.
|
Oldest pending |
The time since the first backlogged file (of each import type) was added to
the queue for uploading. For possible values, see Newest
pending.
|
Total file size |
The sum of file sizes for all the files (of each import type) that are awaiting
upload.
|
IT Asset Management (Cloud)
Current