Versions Compared

Version Old Version 2 New Version 3
Changes made by

Laszlo Frazer

Laszlo Frazer

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • CBS token error - This issue happens usually when the connection string includes the event hub namespace name instead of the event hub name. Both values are usually different and it is easy to mix up both.

  • Delayed events - You can use the @devo_event_enqueued_time value in the table cloud.azure to check the time that the events are queued in Azure.

    Code Block
    from cloud.azure
select eventdate-parsedate(str(jqeval(jqcompile(".\"@devo_event_enqueued_time\""), jsonparse(rawMessage))),"YYYY-MM-DD[T]HH:mm:ss.SSSSSS[Z]","utc") as collector_delay,
parsedate(str(jqeval(jqcompile(".\"@devo_event_enqueued_time\""), jsonparse(rawMessage))),"YYYY-MM-DD[T]HH:mm:ss.SSSSSS[Z]","utc")-parsedate(timestamp,"YYYY-MM-DD[T]HH:mm:ss.SSSSSSS[Z]","utc") as eventhub_delay,
collector_delay+eventhub_delay>1h as problem_detected

    The delayed events can be caused by Event Hub itself (high enqueued time), or by lack of processing capacity of collector. In this case, it is necessary to add more collector instances, or to create a collector for each partition pods.

  • Duplicated events - Adjust the value of the config parameter duplicated_messages_mechanism_value according to your deployment. If you are running several instances, change the value to local.

...