Unable to view GitLab instance application logs on a single host/container install
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Proposal
In GitLab 13, the admin view was removed via Remove logs from the admin pages
Our documentation has user/admin_area/index.html#logs
Logs Since GitLab 13.0, Log view has been removed from the admin dashboard since the logging does not work in multi-node setups and could cause confusion for administrators by displaying partial information.
For multi-node systems we recommend ingesting the logs into services like Elasticsearch and Splunk.
For a single GitLab instance the user now needs access to the GitLab host to view the files locally or that additional customer effort has been done to collect these logs and make them available via another means to the GitLab Instance application administrator with giving host access.
In some cases the administrators of the GitLab application do not have ssh access to the GitLab host which reduces the visibility of log data and requires interaction with other teams which do.
The above merge request which removes the view suggests
A better solution would be to ingest the logs in ES.
Options
- Is using Elasticsearch an option to consider?
- A new UI action to collect logs and make available for download, possible extend to use functionality from gitlabsos and fast-stats
- alternatives to ES
Related issues
- Support Downloading the Logs files from the Admin UI
- Admin Logs UI: Load each log tab asynchronously
- Use latest build logs interface for system logs in the admin panel to improve UX
- UX: /admin/logs pages are not easy to use
There is cross-over between admin/system_info and admin/application_settings/metrics_and_profiling > Self Monitoring but confused by which deployment of GitLab is being used.
From admin/system_info we have
From admin/application_settings/metrics_and_profiling > Self Monitoring
From admin > Monitoring > Logs
