Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 34,943
    • Issues 34,943
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1,268
    • Merge Requests 1,268
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #198050

Closed
Open
Opened Jan 21, 2020 by Dov Hershkovitch@dhershkovitch👀Developer

Support pagination in log explorer

Problem to solve

Log explorer is limited to 500 lines, when a user selects a time range (any time range) it will return only 500 lines, with this limitation it doesn't really matter what is the time range a user selects we'll still see the same results

Intended users

  • Sasha (Software Developer)
  • Devon (DevOps Engineer)
  • Sidney (Systems Administrator)

Further details

The desired user experience is that if a user selects a time range we should display all logs for that time range only. and if the user would like to go beyond the filtered time range, the user would need to select a different range to do so.

Proposal

We should support pagination in the backend in order to allow the user to scroll freely across the selected time range using an Infinite scroll pattern.

We are displaying logs, so the most latest information is displayed at the bottom. So the "infinite scroll" is reverted to display the last items first while scrolling to see the items higher up loads more items.

This pattern is similar scrolling for more chat messages such as Slack or SMS.

Technical Proposal

  • backend Expose elasticsearch pagination parameters following Gitlab pagination pattern.
  • frontend Implement a "reverse" inifinite scroll, this might require a contribution to Gitlab UI's infinite scroll https://gitlab-org.gitlab.io/gitlab-ui/?path=/story/base-infinite-scroll--default

Additional consideration

  • We decided to keep the current experience on showing the latest log entry at the bottom of the screen, scrolling upward if the user want to go back in time.
  • When scrolling downward we noticed that some of the controls and the notification message of installing Elasticsearch disappear. we should address this with a separate issue

Links / references

Edited Nov 16, 2020 by 🤖 GitLab Bot 🤖
Assignee
Assign to
12.9
Milestone
12.9 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab#198050