Publish error messages to a topic

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 1.3.0
    • Affects Version/s: None
    • Component/s: Source
    • None
    • None
    • Needed
    • Hide

      Added support for the following settings:

      errors.tolerance = [none, all]
      Errors tolerance controls: The behavior for tolerating errors during connector operation. 'none' is the default value and signals that any error will result in an immediate connector task failure; 'all' "changes the behavior to skip over problematic records.";

      errors.log.enable=[true,false]
      If true, write each error and the details of the failed operation and problematic record to the Connect application log. This is 'false' by default, so that only errors that are not tolerated are reported.

      errors.deadletterqueue.topic.name="someTopic"
      Whether to output conversion errors to the dead letter queue. Stops poison messages when using schemas, any message will be outputted as extended json on the specified topic. By default messages are not outputted to the dead letter queue. Also requires `errors.tolerance=all`

      Show
      Added support for the following settings: errors.tolerance = [none, all] Errors tolerance controls: The behavior for tolerating errors during connector operation. 'none' is the default value and signals that any error will result in an immediate connector task failure; 'all' "changes the behavior to skip over problematic records."; errors.log.enable= [true,false] If true, write each error and the details of the failed operation and problematic record to the Connect application log. This is 'false' by default, so that only errors that are not tolerated are reported. errors.deadletterqueue.topic.name="someTopic" Whether to output conversion errors to the dead letter queue. Stops poison messages when using schemas, any message will be outputted as extended json on the specified topic. By default messages are not outputted to the dead letter queue. Also requires `errors.tolerance=all`
    • None
    • None
    • None
    • None
    • None
    • None

      In case of failure to process events (conversion failing, retryable errors, etc) on the connector side, we should have the ability to publish a message to an error topic with sufficient details to identify a potential series of missed events.

            Assignee:
            Ross Lawley
            Reporter:
            Davenson Lombard
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: