Hi Nuwan, Maneesha,
I am totally agree that now we have this information and can be provided in
another dashboard.
However, Current analytics is based on normal logs, not based on audit log.
I do not think it is right time to add the feature to read the audit logs,
since it is time to stabilise
Yes, we now have audit logs on the API Manager for API create, update and
remove. The ideal solution is to use these logs to derive those data.
On Tue, Jul 5, 2016 at 1:42 PM, Maneesha Wijesekara
wrote:
> Hi Sajith,
>
> Agreed with how the log analyzer works when an API is
Hi Sajith,
Agreed with how the log analyzer works when an API is updated. But when
considering the user point of view, an API shouldn't be listed in 'Deleted
APIs' list if it's still available. Because a user might get confused when
the statistics in 'Deleted APIs' shows some API that he/she used
Adding Isabelle and Srinath to the email thread.
--
Thanks,
Miyuru Dayarathna
Senior Technical Lead
Mobile: +94713527783
Blog: http://miyurublog.blogspot.com
On Tue, Jul 5, 2016 at 1:11 PM, Sajith Perera wrote:
>
> Hi Maneesha,
>
> Log analyzer purely based on the log events
Hi Maneesha,
Log analyzer purely based on the log events which are generated by a
particular product. For each stat, there are set of keywords and rules in
log lines, which we are identifying as unique for that scenario.
Regarding the above mentioned scenario, if there is an update on an API in
Hi all,
Currently 'API Deployment Stats' in Log Analyzer listed both Deployed APIs
and Deleted APIs. But I've noticed that some available APIs (not yet
deleted) are also listed under 'Deleted APIs' [1]. The reason behind this
is when an API is edited, it will destroyed and again re-deployed. That