Hi Uvindra,

Details in AM_API will be enough for the audit log.
If we want to capture lifecycle state details I understand that we need to
look at registry resources as well.

Thanks.

On Thu, Oct 27, 2016 at 3:21 PM, Uvindra Dias Jayasinha <uvin...@wso2.com>
wrote:

> HI Thilini,
>
> If all you want to check is when an API is added or deleted then the same
> approach of using trigger for AM_API table is enough. But what information
> exactly do you need to collect for the audit?
>
> On 27 October 2016 at 14:23, Thilini Cooray <thili...@wso2.com> wrote:
>
>> Hi,
>>
>> APIM 1.7 does not support audit logs for operations such as API creation
>> and deletion, application creation and deletion.
>> I am looking for alternatives which can be used for collecting audit data.
>>
>> Since application data are only stored in AM_DB, we can collect
>> application related audit data by adding a database trigger for
>> AM_APPLICATION table.
>>
>> However, API details are stored in both AM_DB and Registry DB.
>> Therefore what is the recommended way for collecting audit data for API
>> creation and deletion?
>>
>> Will it be reliable enough to just add a database trigger for AM_API
>> table for insertions and deletions ?
>>
>> Thanks.
>>
>> --
>> Best Regards,
>>
>> *Thilini Cooray*
>> Software Engineer
>> Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20774%20570112>
>> E-mail : thili...@wso2.com
>>
>> WSO2 Inc. www.wso2.com
>> lean.enterprise.middleware
>>
>> _______________________________________________
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
> Regards,
> Uvindra
>
> Mobile: 777733962
>



-- 
Best Regards,

*Thilini Cooray*
Software Engineer
Mobile : +94 (0) 774 570 112 <%2B94%20%280%29%20774%20570112>
E-mail : thili...@wso2.com

WSO2 Inc. www.wso2.com
lean.enterprise.middleware
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to