Page History
This section includes the following topictopics:
...
| Table of Contents | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
The Collector file is an XML file with one or more rows that are generated from user-defined definitions. These data files, collected by the Add-on AppTier Collector, are put in a Collector directory in the <i3_root> for local client harvesting.
...
The following table shows the elements of a Collector file name.
Table C- 1 Elements of a Collector file name
| Element | Description |
|---|---|
| Tech-code | 2-letter technology code (U1, U2, and so on). The technology code is assigned to your Add-on AppTier application during registration and is specified in the ETD file. |
| Monitored-server | Name of monitored (instance) server (for example: _MyServer). The monitored server is installed through AdminPoint. |
| Instance-name | Name of instance (added previously through AdminPoint). |
| Unique-id | A sequence number that is generated by the Insight SDK Collector and ensures the file name is unique. There is no standard or restriction to the sequence number range and format. |
| File extension | Prf is used for performance data; avl is used for availability data (not currently supported). |
The body of the Collector file contains multiple row elements, each of them representing a summary of a distinct activity, collected after a default 15-minute timeslice. The entities and counters are defined as child elements with text values.
...
The following table specifies the attributes for the root <rowset> element.
Table C- 2 Root <rowset> element attributes
| Rowset Attribute Name | Description |
|---|---|
| Savvy | A 2-letter technology code (U1, U2, and so on). The technology code is assigned to your Add-on AppTier application during registration, and is specified in the ETD file. |
| Instance | Instance name (added earlier through AdminPoint). |
| Server | Monitored (instance) server name. For example: _MyServer. The monitored server is installed through AdminPoint. |
About XML Collector file rows
The body of an XML Collector file is a series of <row> elements. Each row specifies the activation of a unique activity in the Add-on AppTier during a 15-minute time slice.
...
- Timestamp field. Values should be specified by GMT time zone. Mandatory format: YYYY-MM-DD-HH24:MM:SS
- Entities. Values should be enclosed with the following: <! [CDATA [….] ] >
- Counters. Service time counters must be reported in the following format: sss.mmm where seconds and milliseconds with a decimal point have a character dot.
About file closure and stamp
The SDK Collector file cannot be harvested to the Precise FocalPoint server until the file is closed and stamped by the SDK Collector. The SDK Collector closes and stamps the file to signal file readiness for subsequent processing and loading to the PMDB.
...
MS_MailInstance-1_MailServer-1_1189403.pok
where file size is 0 KB.
About time slices and activity summaries
Collector files are harvested at time periods having fixed intervals. These time intervals are called time slices and their length is fixed at 15 minutes. The Precise harvester waits one minute, after a time slice has passed, and searches for new files to move to the Precise FocalPoint server.
...
The Insight SDK Collector follows this standard when in ARM collection mode. However, this standard is not mandatory for SDK Collector file mode. The Collector can create as many files in the same time slice and use whatever aggregation mechanism needed. The SDK Collector is responsible to manage such issues as footprint, file size, and scalability.
| Scroll Ignore | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Newtabfooter |
|
...
Precise. Performance intelligence from click to storage. Learn more > >
...
...