How long will events be kept?


iamflying
 

Hi all,

Recently, I am playing with Event API[1]. I am wondering if the events will
be kept persistent for ever or will be purged automatically based on some
policy. Who can share some details?

Meanwhile, I found there is no event audit.app.stop. It was
audit.app.update when I stopped the app. Is it a code bug or documentation
bug?
{
"metadata": {
"guid": "ff81faa1-ce42-415d-a482-defc27524ef4",
"url": "/v2/events/ff81faa1-ce42-415d-a482-defc27524ef4",
"created_at": "2015-07-31T05:27:18Z",
"updated_at": null
},
"entity": {
"type": "audit.app.update",
"actor": "7d85d3d1-9d23-4ba4-8908-7f634f37d0d4",
"actor_type": "user",
"actor_name": "admin",
"actee": "b4953111-9913-4fbf-835a-a6f618c6a59d",
"actee_type": "app",
"actee_name": "simple-java",
"timestamp": "2015-07-31T05:27:18Z",
"metadata": {
"request": {
"state": "STOPPED"
}
},
"space_guid": "d9e4eb09-6b31-401b-87ea-2305364f7a1a",
"organization_guid": "79f25032-0f56-4c7c-86cc-d5c6a67ec300"
}
},




[1] http://apidocs.cloudfoundry.org/214/events/list_app_update_events.html


Gwenn Etourneau
 

Event are purged based on some value put on your manifest :

cc.app_events.cutoff_age_in_days:
description: "How old an app event should stay in cloud controller
database before being cleaned up"
default: 31
cc.app_usage_events.cutoff_age_in_days:
description: "How old an app usage event should stay in cloud
controller database before being cleaned up"
default: 31
cc.audit_events.cutoff_age_in_days:
description: "How old an audit event should stay in cloud controller
database before being cleaned up"
default: 31
cc.failed_jobs.cutoff_age_in_days:
description: "How old a failed job should stay in cloud controller
database before being cleaned up"
default: 31

On Fri, Jul 31, 2015 at 3:54 PM, Guangcai Wang <guangcai.wang(a)gmail.com>
wrote:

Hi all,

Recently, I am playing with Event API[1]. I am wondering if the events
will be kept persistent for ever or will be purged automatically based on
some policy. Who can share some details?

Meanwhile, I found there is no event audit.app.stop. It was
audit.app.update when I stopped the app. Is it a code bug or documentation
bug?
{
"metadata": {
"guid": "ff81faa1-ce42-415d-a482-defc27524ef4",
"url": "/v2/events/ff81faa1-ce42-415d-a482-defc27524ef4",
"created_at": "2015-07-31T05:27:18Z",
"updated_at": null
},
"entity": {
"type": "audit.app.update",
"actor": "7d85d3d1-9d23-4ba4-8908-7f634f37d0d4",
"actor_type": "user",
"actor_name": "admin",
"actee": "b4953111-9913-4fbf-835a-a6f618c6a59d",
"actee_type": "app",
"actee_name": "simple-java",
"timestamp": "2015-07-31T05:27:18Z",
"metadata": {
"request": {
"state": "STOPPED"
}
},
"space_guid": "d9e4eb09-6b31-401b-87ea-2305364f7a1a",
"organization_guid": "79f25032-0f56-4c7c-86cc-d5c6a67ec300"
}
},




[1] http://apidocs.cloudfoundry.org/214/events/list_app_update_events.html


_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev