auth.ping
- Juan Tomás Alonso Nieto (Deactivated)
- Laszlo Frazer
- Former user (Deleted)
Introduction
Tags beginning with auth.ping identify events generated by authentication services belonging to PingIdentity.
Valid tags and data tables
The full tag must have 4 levels. The first two are fixed as auth.ping. The third level identifies the type of events sent, and the fourth level indicates the event subtype.
These are the valid tags and corresponding data tables that will receive the parsers' data:
Product / Service | Tag | Data table |
|---|---|---|
PingFederate |
|
|
|
| |
|
| |
PingID |
|
|
For more information, read more About Devo tags.
How is the data sent to Devo?
Logs may be sent with the Devo relay. Example relay rules:
Source message:
Source data: ^\d{4}-\d{2}-\d{2}\s\d{2}:\d{2}:\d{2},\d{3}\strackingid=
Source tag:
Target tag: auth.ping.federate.audit
Sent without syslog tag: true Source message:
Source data: ^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2},\d{3}\|
Source tag:
Target tag: auth.ping.federate.security_audit
Sent without syslog tag: true Source message:
Source data:
Source tag:
Target tag: auth.ping.id.mfa
Sent without syslog tag: trueTable structure
These are the fields displayed in these tables: