Uploaded image for project: 'OpenShift Migration Toolkit for Containers'
  1. OpenShift Migration Toolkit for Containers
  2. MIG-521

Establish abnormal event reporting pattern to support tracking and troubleshooting

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Major Major
    • MTC 1.4.2
    • None
    • None
    • False
    • False
    • ToDo
    • Undefined

      During our discussions about direct migration network validation, we'd like to be able to "classify" errors or warnings into specific buckets. So for example, because direct migration network validation isn't a clear cut case of "if this happens, then it's a network problem", we have to fall back on some kind of a heuristic. Once detected, it would be very useful for us to know how many users are actually facing problems satisfying the direct migration requirements, and we'd also like to be able to point them to a troubleshooting document that can help guide them to resolving their problems themselves.

      A generic error classification and reporting system would be very useful for that.

      The thought is to use something in the spirit of error codes (not exactly error codes), but having a bounded and well defined set of buckets that error/warning conditions can fall into. Ex:

      conditions:

      • craneErrorType: DirectNetworkFailure
        message: <some human readable>

      Maybe there's a well defined set of craneErrorTypes that we can document. The bounded cardinality would allow us to plug into metrics.

              alpatel07 Alay Patel (Inactive)
              ernelson@redhat.com Erik Nelson (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: