Metrics produced by the Log File Reader feature.
Line count metrics
For each collection cycle, the reader counts the number of matching lines per unique combination of key alias and extract field values.
Path pattern:
Hpa|LogFile|{reader}|{keyAlias}|{extractField1}|{extractField2}|...:value
-
{reader}— the readernamefrom the configuration -
{keyAlias}— the alias of the matched key value (or the raw value if no alias is defined) -
{extractFieldN}— each extracted field value, in order
If no extract fields are configured, the path is simply:
Hpa|LogFile|{reader}|{keyAlias}:value
The value is the number of matching lines seen during the collection interval (PER_INTERVAL semantics).
Examples:
| Configuration | Metric path | Meaning |
|---|---|---|
reader CTM_DAILY, key alias OK, extract fields JOB_A and PROD |
Hpa|LogFile|CTM_DAILY|OK|JOB_A|PROD:value |
Number of lines with status OK for job JOB_A in PROD |
reader APP_ERRORS, key value ERROR, no extract fields |
Hpa|LogFile|APP_ERRORS|ERROR:value |
Number of ERROR lines |
Diagnostic metric
Each reader also reports the number of files currently matching its file-name-regex:
Hpa|LogFile|{reader}:filesMatched
Value sanitization
Special characters in extracted values are replaced to produce valid metric paths:
-
|and:are replaced with_ - Empty values are replaced with
(empty)