Integration-Related Events¶
Through events related to integrations, you can view anomalies and recoveries that occur during cloud collector operation and troubleshoot data collection issues.
View Related Events¶
Integrations with a cloud collector installed and Func configured display a Related Events entry.
- Go to the Integrations page and locate the integration card you want to view;
- Click Related Events on the card to open the Related Events tab in the integration details;
- Click an event to view the anomaly cause or recovery status.
Query in Event Center¶
- Go to Event Center > All Events and select the time range to query;
- Enter the following conditions in the search bar to filter integration collection events;
- Append conditions such as cloud provider, integration product, cloud account, or event status as needed, then click an event to view details.
These two conditions must be used together: df_source:monitor includes other monitoring events, and it can filter integration collection events only when combined with df_monitor_type:integration_collection.
Common Filter Fields¶
Based on the conditions above, you can append the following conditions with AND:
| Query Purpose | Field | Filter Example |
|---|---|---|
| View only anomaly events | df_status |
df_status:error |
| View only recovery events | df_status |
df_status:ok |
| Query by cloud provider | provider |
provider:aws, for AWS |
| Query by integration product | product |
product:ec2, for the EC2 integration |
| Query by cloud account | cloud_account_uuid_suffix |
cloud_account_uuid_suffix:a25ec4cd, using the last 8 characters of the cloud account UUID |
| Query by actual collector | collector |
collector:aws_cloudwatch |
For example, to query anomaly events for the AWS EC2 integration:
df_source:monitor AND df_monitor_type:integration_collection AND provider:aws AND product:ec2 AND df_status:error
To restrict to a cloud account, append AND cloud_account_uuid_suffix:a25ec4cd. Replace the account suffix in the example with the actual value, which can be copied from the corresponding field in the event details.
product indicates the installed integration product, while collector indicates the collector that actually performs collection; the two may differ. If an event does not include the cloud provider, product, or account suffix fields, you can filter using the collector, dff_script_id (script ID), or dff_func_id (function ID) fields available in the event details.
For more search methods, see Explorer Search.
View Event Details¶
When a collection anomaly occurs, you can view error messages in the event details, along with the available cloud account, region, API operation, error code, and request ID, to locate the collection task that failed and troubleshoot the cause. The specific content displayed depends on the information included in the event.
Anomalies and Recovery¶
| Event | Description |
|---|---|
| Anomaly | The cloud collector encountered an API call anomaly or collection execution anomaly; open the details to view the cause |
| Recovery | A previously anomalous collection request has executed successfully, and the corresponding anomaly has recovered |
Different anomalies each show their own recovery status; the recovery of one anomaly does not mean other anomalies have also recovered. Historical anomaly events are retained after recovery for backtracking issues.
When viewing events, consider the query time range and current collection results; the absence of recovery events within the query range does not necessarily mean the current collection is still anomalous.