Hi Josh,

Unfortunately it is not. The server/message logs go wherever the environment the service is running in, which in PAaaS deployments is whatever the underlying MCSP dictates. AFAIK in PAaaS as an end-user you have no access to the collected logs/the log collector, you can only view them through PAA  as there is no API available in PA that serves them up.

In a PACC deployment (read: you deploying PA in your Kubernetes cluster somewhere) on the other hand, you'd have more control technically as you'd be collecting using the log collector that cluster is set up with, and access to those could be granted to those that would require it, if you were granted that access, you'd be able to consume them directly through the log collector's API as well.

In a PA 3.1 setup the TM1 logs are, by default, collected and written to a file but also there can configure TM1 to push to a log collector of your choosing (LogStash/ELK, LogDNA, CloudWatch etc. etc.) and build or use existing UIs to interact/query/take action as things happen and get pushed to such collectors.

Thank you for confirming. 

Hi Josh,

Unfortunately it is not. The server/message logs go wherever the environment the service is running in, which in PAaaS deployments is whatever the underlying MCSP dictates. AFAIK in PAaaS as an end-user you have no access to the collected logs/the log collector, you can only view them through PAA  as there is no API available in PA that serves them up.

In a PACC deployment (read: you deploying PA in your Kubernetes cluster somewhere) on the other hand, you'd have more control technically as you'd be collecting using the log collector that cluster is set up with, and access to those could be granted to those that would require it, if you were granted that access, you'd be able to consume them directly through the log collector's API as well.

In a PA 3.1 setup the TM1 logs are, by default, collected and written to a file but also there can configure TM1 to push to a log collector of your choosing (LogStash/ELK, LogDNA, CloudWatch etc. etc.) and build or use existing UIs to interact/query/take action as things happen and get pushed to such collectors.

Hi @Hubert Heijkers, do you have an estimated timeline for when Server and Audit logs will be available via the REST API in PAaaS / v12?

Thank you for confirming. 

Hi Josh,

Unfortunately it is not. The server/message logs go wherever the environment the service is running in, which in PAaaS deployments is whatever the underlying MCSP dictates. AFAIK in PAaaS as an end-user you have no access to the collected logs/the log collector, you can only view them through PAA  as there is no API available in PA that serves them up.

In a PACC deployment (read: you deploying PA in your Kubernetes cluster somewhere) on the other hand, you'd have more control technically as you'd be collecting using the log collector that cluster is set up with, and access to those could be granted to those that would require it, if you were granted that access, you'd be able to consume them directly through the log collector's API as well.

In a PA 3.1 setup the TM1 logs are, by default, collected and written to a file but also there can configure TM1 to push to a log collector of your choosing (LogStash/ELK, LogDNA, CloudWatch etc. etc.) and build or use existing UIs to interact/query/take action as things happen and get pushed to such collectors.

Hi Vlad,

Server logs (a.k.a. Message logs), as per the cloud style infrastructure I referenced above, aren't even retained by TM1, they are sent (fire and forgot) to whatever log collector in your setup.

Audit logs, not the once you used to but rather a newly designed - driven by our new underlying infrastructure, we have plans for but can't guarantee, given the high value topics we are driving to get out this year, that it will be this year. But, as a heads up, even there we might end up choosing to use log collector infrastructure to collect those logs rather than having TM1 retain and manage them (tbd).

Hi @Hubert Heijkers, do you have an estimated timeline for when Server and Audit logs will be available via the REST API in PAaaS / v12?

Thank you for confirming. 

Hi Josh,

Unfortunately it is not. The server/message logs go wherever the environment the service is running in, which in PAaaS deployments is whatever the underlying MCSP dictates. AFAIK in PAaaS as an end-user you have no access to the collected logs/the log collector, you can only view them through PAA  as there is no API available in PA that serves them up.

In a PACC deployment (read: you deploying PA in your Kubernetes cluster somewhere) on the other hand, you'd have more control technically as you'd be collecting using the log collector that cluster is set up with, and access to those could be granted to those that would require it, if you were granted that access, you'd be able to consume them directly through the log collector's API as well.

In a PA 3.1 setup the TM1 logs are, by default, collected and written to a file but also there can configure TM1 to push to a log collector of your choosing (LogStash/ELK, LogDNA, CloudWatch etc. etc.) and build or use existing UIs to interact/query/take action as things happen and get pushed to such collectors.

Thanks @Hubert Heijkers!

Would you be able to point me to any relevant documentation or briefly explain whether there is any supported way to configure or integrate with a log collector in IBM PAaaS, particularly for forwarding logs to third-party applications like SPACE?

Appreciate your insight as always.

Hi Vlad,

Server logs (a.k.a. Message logs), as per the cloud style infrastructure I referenced above, aren't even retained by TM1, they are sent (fire and forgot) to whatever log collector in your setup.

Audit logs, not the once you used to but rather a newly designed - driven by our new underlying infrastructure, we have plans for but can't guarantee, given the high value topics we are driving to get out this year, that it will be this year. But, as a heads up, even there we might end up choosing to use log collector infrastructure to collect those logs rather than having TM1 retain and manage them (tbd).

Hi @Hubert Heijkers, do you have an estimated timeline for when Server and Audit logs will be available via the REST API in PAaaS / v12?

Thank you for confirming. 

Hi Josh,

Unfortunately it is not. The server/message logs go wherever the environment the service is running in, which in PAaaS deployments is whatever the underlying MCSP dictates. AFAIK in PAaaS as an end-user you have no access to the collected logs/the log collector, you can only view them through PAA  as there is no API available in PA that serves them up.

In a PACC deployment (read: you deploying PA in your Kubernetes cluster somewhere) on the other hand, you'd have more control technically as you'd be collecting using the log collector that cluster is set up with, and access to those could be granted to those that would require it, if you were granted that access, you'd be able to consume them directly through the log collector's API as well.

In a PA 3.1 setup the TM1 logs are, by default, collected and written to a file but also there can configure TM1 to push to a log collector of your choosing (LogStash/ELK, LogDNA, CloudWatch etc. etc.) and build or use existing UIs to interact/query/take action as things happen and get pushed to such collectors.