auth.ping

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:

For more information, read more About Devo tags.

How is the data sent to Devo?

Audit logs may be sent with the Devo relay. Example relay rule:

         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

Table structure

These are the fields displayed in these tables: