Skip to content

Print container logs in the final error report #287

@distorhead

Description

@distorhead

The problem:

  • container exits with non-zero error code, because there is some error in the application;
  • user sees some "container has been exited with non-zero code" in the end of multitracker log;
  • user needs to see application logs to fix the problem;
  • application logs has been printed somewhere in the middle of multitracker logs, so user need to search these logs to fix application problems.

Solution: multitracker should print failed application logs, events and other information in the end of tracking log giving user all needed information immediately.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions