| Name | Type | Description | Notes |
|---|---|---|---|
| DefaultTopics | AuditLogConfigDefaultTopics | [optional] | |
| Routes | Pointer to map[string]AuditLogConfigRouteCategories | Events are matched to exactly one of these route patterns (or else to the ``default_topics``). The route patterns can be any valid Confluent resource name (CRN), or even a CRN containing wildcards. The most specific pattern that matches an event will be chosen. Consider these example route patterns that match events on Kafka topic resources. They are ordered here from most to least specific: ``crn://mds1.example.com/kafka=abcde_FGHIJKL-01234567/topic=clicks`` ``crn://mds1.example.com/kafka=abcde_FGHIJKL-01234567/topic=`` ``crn://mds1.example.com/kafka=/topic=clicks`` ``crn://mds1.example.com/kafka=*/topic=`` ``crn:///kafka=abcde_FGHIJKL-01234567/topic=clicks`` ``crn:///kafka=/topic=`` For a CRN pattern to match a CRN, the Authority sections must match and the CRN pattern and the CRN must have all of the same path element types in the same order. The Authority section of a CRN is between the second and third slash ("mds1.example.com" in ``crn://mds1.example.com/kafka=/topic=``). It may be left empty (as in ``crn:///kafka=_/topic=*``). A CRN pattern with an empty Authority section matches a CRN with ANY Authority. The converse is not true: A CRN pattern with a non-empty Authority will not match a CRN with an empty Authority. A resource with an empty Authority CRN can only be matched by a CRN pattern with an empty Authority. So an event on the resource with the CRN... ``crn://confluent.cloud/kafka=abcde_FGHIJKL-01234567/topic=clicks`` ... would not match a route with pattern ... ``crn://confluent.cloud/kafka=abcde_FGHIJKL-01234567`` ... because they do not have matching path element types. Once the most specific matching route for an event is determined, it is then matched within that route to exactly one event category, and then based on whether it was "allowed" or "denied", matched to exactly one destination topic (or discarded, if the rule's destination topic name is the empty string). If the category rule's destination topic is ``null`` then it either falls through to the ``default_topics`` (for ``authentication``, ``authorize``, and ``management`` categories), or is discarded (which is the default for all other categories of events). | [optional] |