Skip to content

Commit 4a64283

Browse files
authored
Merge pull request cloudfoundry#70 from gberche-orange/patch-1
Additional example of audit event query
2 parents b9dac92 + 39af85f commit 4a64283

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

managing-cf/audit-events.html.md.erb

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -141,6 +141,10 @@ A user is able to query the events endpoint with various filters. For example, a
141141

142142
Allowed filters are enumerated on the [API documentation](https://apidocs.cloudfoundry.org/latest-release/events/list_all_events.html).
143143

144+
The following example illustrates a query with multiple filters combined: fetch `audit.app.unmap-route` events in a given period of time
145+
146+
`cf curl '/v2/events?q=type:audit.app.unmap-route&q=timestamp>2019-02-06T01:08:24Z&q=timestamp<2019-02-08T01:08:24Z&order-by=timestamp'`
147+
144148
### <a id='ext-auditing'></a> External Auditing Warehouse
145149

146150
For auditing and compliance reasons, some operators may wish to keep a record of all audit events that have occured. Because audit events expire and may be purged during a deploy, these operators must maintain an external data warehouse. This way they can store and access events across expiration events and conform to their own compliance requirements.

0 commit comments

Comments
 (0)