Introduction
The tags beginning with iam.hitachi identify events generated by Hitachi ID products.
Tag structure
The full tag must have four levels. The first two are fixed as iam.hitachi. The third and fourth levels identify the type and subtype of events sent.
Technology | Brand | Type | Subtype |
|---|---|---|---|
iam | hitachi | password | events |
Therefore, the valid tags and tables include:
- iam.hitachi.password.events
How is the data sent to Devo?
You can send the logs generated by Hitachi ID using the tool NXLog.
Log samples
The following are sample logs sent to each of the iam.hitachi tags:
| Tag | Log sample |
|---|---|
| iam.hitachi.password.events | '2021-02-24 17:01:16.396 localhost=127.0.0.1 iam.hitachi.password.events: default[psf.exe(8028,12224)] User failed to identify.|Profile=|Target=PSYNCH|Identity=L00390135|Reason=Not Found' |
And this is how the log would be parsed:
Field | Value | Type |
|---|---|---|
hostchain |
|
|
tag |
|
|
layer |
|
|
module |
|
|
pid |
|
|
parent_pid |
|
|
message |
|
|
type |
|
|
profile |
|
|
target |
|
|
identity | 'L00390135' |
|
reason |
|
|
rawMessage |
|
|