Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 43,875
    • Issues 43,875
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,386
    • Merge requests 1,386
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #29121
Closed
Open
Created May 30, 2019 by Joshua Lambert@joshlambertMaintainer

Rename job trace to job log

Problem statement

Currently we have a Job Traces for CI/CD, as well as Tracing (Jaeger). These two terms can be quite confusing, as a user who hears the words "tracing" may be confused about what we are referring to.

We should look for ways to disambiguate these two terms.

Job Tracing: https://docs.gitlab.com/ee/administration/job_traces.html#new-live-trace-architecture Tracing: https://docs.gitlab.com/ee/user/project/operations/tracing.html

Solution

Tracing is a fairly established industry term for observability, and is therefore a term that we should continue to use for that feature set. Job Traces is a better a candidate for disambiguation.

Job Logs

While this could be confusing with our upcoming logging features of GitLab, there are some benefits. First, job logs and application logs behave fairly similarly, and are similar concepts.

Other services seem to use this general term as well: https://docs.microsoft.com/en-us/rest/api/azure/devops/build/builds/get%20build%20logs?view=azure-devops-rest-5.0

Last, there may be some value in offering a centralized/aggregated version of these build logs, using our upcoming logging service. This could aid forensics and other use cases, for example.

Edited Oct 21, 2019 by Jason Yavorska
Assignee
Assign to
Time tracking