Let us know how we can make Jedox even better!
Dear Jedox,
I believe it is very useful to access the log files within the integrator. However, accessing the log files is no longer possible due to Kubernetes infra. It would be nice to have an alternative.
Would it be possible to create an API for the cloud console logs? So that the log file are accessible.
Kind regards,
Sander Lelivelt
CPM Consultant | Aexis NL
Thanks for this idea. We think it is a good one. We have started an internal process for the implementation of this feature. Watch this space!
Regarding the olap databases it's already possible to have an API. When Audit is activated, cell changes are saved in a sqlite database located in the folder "/Data/<dbname>/". It's straight forward to access it in the integrator, but you have to map the identifiers to the element names (this mapping can be retrieved from the file "database-<verylongnumber>.csv" in the same folder).
So important to measure adoption !
a key feature expected
I have many customers who used the logs to create an application usage dashboard and reports. Since the OnPremise migration to the Cloud this is no longer possible and it really feels like a regression. Besides, dashboards from the Jedox team exist on the same principle and are therefore now unusable.
I have client that would like to automate the download of the Server logs to scan and filter for key words. Optimally there would be an alert sent out for key words. Also details such as individual logins could be downloaded via an integrator load to an IT cube that populates an IT dashboard. There is a lot that can be done with this information.
Further to the comment below, an API for logs would allow the client to use a SIEM tool to read and monitor Jedox logs. We have a customer using Perch for this purpose.
This would be a really helpful feature!
the management of the logs has been changed 3 times in the past 2 years : before it was accessible over the web interface, then also over the SFTP access, then over the SFTP they disappeared, and then over the web interface too...
the logs over the cloud console are really not practical (truncated strings for PHP logs for instance...) and must be exported to be seen correctly
such an API would be really helpful because one can retrieve the logs from any preferred client