Questions about /v2/events


Piotr Przybylski <piotrp@...>
 

Hi,
I have couple of questions related to events that I could not find in the docs. 
There are two /v2/events defined in the docs [1] - audit.app.start and audit.app.stop that don't seem to be
emitted - at least for cf 221. Is there a specific scenario to get these triggered? When starting the application 
we get the audit.app.update with {"request":{"state":"STARTED"}} (and app usage event). 

The audit.app.update event is emitted for several user actions - above start/stop, rename, application push - is
there a way to differentiate between all these actions ? Sometimes it can be done using metadata of the 
event, eg start/stop but others have just the application name in the event metadata (push and rename). 
Piotr



Dieu Cao <dcao@...>
 

Hi Piotr,

Those events are associated with starting/stopping /v3/apps in support of
application process types.
That work is still experimental and can be tracked here:
https://www.pivotaltracker.com/epic/show/1334418

With the v3 api we'll be creating more explicit audit events for the
different actions.
With the v2 api, the best way to differentiate is with a combination of
type and the metadata.

-Dieu
CF CAPI PM

On Tue, Dec 1, 2015 at 10:30 AM, Piotr Przybylski <piotrp(a)us.ibm.com> wrote:

Hi,
I have couple of questions related to events that I could not find in the
docs.
There are two /v2/events defined in the docs [1] - audit.app.start and
audit.app.stop that don't seem to be
emitted - at least for cf 221. Is there a specific scenario to get these
triggered? When starting the application
we get the audit.app.update with {"request":{"state":"STARTED"}} (and app
usage event).

The audit.app.update event is emitted for several user actions - above
start/stop, rename, application push - is
there a way to differentiate between all these actions ? Sometimes it can
be done using metadata of the
event, eg start/stop but others have just the application name in the
event metadata (push and rename).


[1] -
http://apidocs.cloudfoundry.org/225/events/list_app_start_events.html

Piotr



Piotr Przybylski <piotrp@...>
 

Hi Dieu, 
thank you for the clarification. Is the list of events [1] for v3 api still evolving ? 

[1] - http://apidocs.cloudfoundry.org/225/events/list_all_events.html

Piotr



-----Dieu Cao <dcao@...> wrote: -----
To: "Discussions about Cloud Foundry projects and the system overall." <cf-dev@...>
From: Dieu Cao <dcao@...>
Date: 12/01/2015 01:10PM
Subject: [cf-dev] Re: Questions about /v2/events

Hi Piotr,

Those events are associated with starting/stopping /v3/apps in support of application process types.
That work is still experimental and can be tracked here: https://www.pivotaltracker.com/epic/show/1334418

With the v3 api we'll be creating more explicit audit events for the different actions.
With the v2 api, the best way to differentiate is with a combination of type and the metadata.

-Dieu
CF CAPI PM

On Tue, Dec 1, 2015 at 10:30 AM, Piotr Przybylski <piotrp@...> wrote:
Hi,
I have couple of questions related to events that I could not find in the docs. 
There are two /v2/events defined in the docs [1] - audit.app.start and audit.app.stop that don't seem to be
emitted - at least for cf 221. Is there a specific scenario to get these triggered? When starting the application 
we get the audit.app.update with {"request":{"state":"STARTED"}} (and app usage event). 

The audit.app.update event is emitted for several user actions - above start/stop, rename, application push - is
there a way to differentiate between all these actions ? Sometimes it can be done using metadata of the 
event, eg start/stop but others have just the application name in the event metadata (push and rename). 
Piotr





Dieu Cao <dcao@...>
 

Yes, it's still evolving.

A couple of additional stories for example include adding events for
droplets [1] and processes [2]

[1] https://www.pivotaltracker.com/story/show/101936042
[2] https://www.pivotaltracker.com/story/show/101936284

On Wed, Dec 2, 2015 at 9:55 AM, Piotr Przybylski <piotrp(a)us.ibm.com> wrote:

Hi Dieu,
thank you for the clarification. Is the list of events [1] for v3 api
still evolving ?

[1] - http://apidocs.cloudfoundry.org/225/events/list_all_events.html

Piotr



-----Dieu Cao <dcao(a)pivotal.io> wrote: -----
To: "Discussions about Cloud Foundry projects and the system overall." <
cf-dev(a)lists.cloudfoundry.org>
From: Dieu Cao <dcao(a)pivotal.io>
Date: 12/01/2015 01:10PM
Subject: [cf-dev] Re: Questions about /v2/events


Hi Piotr,

Those events are associated with starting/stopping /v3/apps in support of
application process types.
That work is still experimental and can be tracked here:
https://www.pivotaltracker.com/epic/show/1334418

With the v3 api we'll be creating more explicit audit events for the
different actions.
With the v2 api, the best way to differentiate is with a combination of
type and the metadata.

-Dieu
CF CAPI PM

On Tue, Dec 1, 2015 at 10:30 AM, Piotr Przybylski <piotrp(a)us.ibm.com>
wrote:

Hi,
I have couple of questions related to events that I could not find in the
docs.
There are two /v2/events defined in the docs [1] - audit.app.start and
audit.app.stop that don't seem to be
emitted - at least for cf 221. Is there a specific scenario to get these
triggered? When starting the application
we get the audit.app.update with {"request":{"state":"STARTED"}} (and app
usage event).

The audit.app.update event is emitted for several user actions - above
start/stop, rename, application push - is
there a way to differentiate between all these actions ? Sometimes it can
be done using metadata of the
event, eg start/stop but others have just the application name in the
event metadata (push and rename).


[1] -
http://apidocs.cloudfoundry.org/225/events/list_app_start_events.html

Piotr