Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 2 Current »

Azure concerns

Capacity and scaling

Connectivity

Collector concerns

Error type

Error ID

Error message

Cause

Solution

InitVariablesError

1

Invalid start_time_in_utc: {ini_start_str}. Must be in parseable datetime format.

The configured start_time_in_utc parameter is a non-parseable format.

Update the start_time_in_utc value to have the recommended format as indicated in the guide.

InitVariablesError

2

Invalid start_time_in_utc: {ini_start_str}. Must be in the past.

The configured start_time_in_utc parameter is a future date.

Update the start_time_in_utc value to a past datetime.

PullError

350

Could not match tag to record and no default tag provided: {record}

Advanced tagging configured but no default tag provided and record did not match any of tag pathways

Provide default tag in advanced tag mapping object

ApiError

401

An error occurred while trying to authenticate with the Azure API. Exception: {e}

The collector is unable to authenticate with the Azure API.

Check the credentials and ensure that the collector has the necessary permissions to access the Azure API.

ApiError

410

An error occurred while trying to check if container '{container_name}' exists. Ensure that the blob storage account name or connection string is correct. Exception: {e}

The collector was unable to locate the specified blob storage container name.

Ensure the container exists and the credentials have READ access to the container.

ApiError

411

An error occurred while trying to check if container '{container_name}' exists. Ensure that the application has necessary permissions to access the containers. Exception: {e}

The collector was unable to access the specified blob storage container name.

Ensure the container exists and the credentials have READ access to the container.

ApiError

412

An error occurred while trying to create container '{container_name}'. Ensure that the application has necessary permissions to create containers. Exception: {e}

The collector was unable to create the container for the auto discover service and the user indicated to use Azure Blob Storage checkpointing.

Ensure the credentials have WRITE access to the container storage account.

ApiError

420

An error occurred while trying to get consumer group '{consumer_group_name}'. Exception: {e}

The collector was unable to access the specified consumer group name.

Ensure the consumer group exists and the credentials have READ access to the consumer group.

ApiError

421

An error occurred while trying to create consumer group '{consumer_group_name}'. Ensure that the application has necessary permissions to create consumer groups. Exception: {e}

The collector was unable to create the consumer group for the auto discover service.

Ensure the credentials have WRITE access to the event hub namespace or use the $Default consumer group.

Typical issues

  • 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. 

    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.

  • 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.

Metadata

The collector adds some metadata to the events that can be useful for issue diagnose. This metadata can be found in the cloud.azure table:

  • devo_record_idx: identificator for the event, composed by the event secuence number and a ordinal number

  • devo_record_hash_id: hash value of the whole record. If two records have the same value, they are exactly equal.

  • devo_event_offset: offset value for the record in the EventHub queue

  • devo_event_enqueued_time: time in which the event was enqueued in the EventHub

  • devo_event_sequence_number: secuence number in the EventHub

  • devo_eh_partition_id: source partition for the event

  • devo_eh_consumer_group: source consumer group

  • devo_eh_fully_qualified_namespace: source namespace dor the event

  • devo_pulling_id: epoch timestamp corresponding the time the event was sent to Devo by the collector. It should be close to the eventdate of the event.

More details about the meaning of this metadata can be found in Microsoft EventHub webpage.

  • No labels