Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gstreamer gstreamer
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 745
    • Issues 745
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 379
    • Merge requests 379
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamer
  • gstreamergstreamer
  • Issues
  • #201
Closed
Open
Created Oct 25, 2016 by Bugzilla Migration User@bugzilla-migration

core(debug): hard to distinguish related log at multi-instance env

Submitted by Eunhae Choi

Link to original bug (#773463)

Description

This is for debug env.

When we do debug with log message, it is hard to recoginize which element/object is included in which pipeline in multi-instance environment.

We've added family-id for grouping for each pipeline at downstream (I've attached the patch).

To get better idea and make it public, I registered this bug.
Please share your idea and suggest better solution.

Thank you.

Assignee
Assign to
Time tracking