Activity Graphs
Activity graphs are trend line bar graphs that Hevo uses to provide a visual representation of the data replication progress. You can use activity graphs to view the number of Events ingested and loaded to the Destination, and the average latency of the Destination.
Pipeline Activity Graphs
Pipeline activity graphs in the Pipeline Overview page provide a snapshot of the number of Events that are processed in different stages of a Pipeline which are:
- Ingestion
- Transformation
- Schema Mapping
- Loading
The total count sums up the Events processed in that stage for the selected duration. Each bar in the graph represents one Pipeline run. The different colors in the graph help you get clarity regarding your Events quota usage in terms of incremental (billable) vs historical (free) Events.
Billable Events
Billable Events are the new and modified Events created post-Pipeline creation. These Events are represented by the darker shade of blue in the graph. Loading of these Events to your Destination consumes your Events quota.
Historical Events
Historical Events are all the pre-existing Events in the Source before the Pipeline was created and are represented by light blue color in the graph. Hevo loads all your historical data for free when you create the Pipeline or if you restart the historical load at any time.
Working with graphs
Here are a few things you can do to get the most out of your graphs:
-
Read the Events count: Hover over the bars to get the exact count of billable and historical Events that have processed in that stage on each run of the Pipeline.
-
View Events count for different durations: You can view the number of ingested Events for different durations. Default value: 24 hours. The total Events count changes for the selected duration. For example, a total of 393 Events were ingested in the last 24 hours in the image below.
Destination Activity Graphs
Destination activity graphs provide you a snapshot of the current status of tasks in the Destination. Hevo provides you two types of Destination activity graphs:
- Load
- Latency
Load graph
This bar graph displays the number of Events loaded to the Destination in a certain time period. Each bar represents the number of Events loaded per Destination load. The bar uses two colors:
- Light blue: Represents the historical (free) Events loaded to the Destination.
- Dark blue: Represents the incremental (billable) Events loaded to the Destination.
The total count displayed on the graph sums up the Events loaded for the duration selected in the top right of the Destination Activity section.
Here are a few things you can do to get the most out of your load graphs:
-
Know the historical and billable Events count: Hover over the Total Events count to get the count of billable and historical Events for the selected time duration.
Hovering over each bar gets you the exact count of billable and historical Events that have loaded in each Destination load.
Load graphs are also displayed for every Destination table.
-
View Events count for different durations: You can view the number of loaded Events for different durations. Default value: 24 hours. The total Events count changes as per the selected duration. For example, a total of 44.82k Events were ingested in the last 24 hours in the image below.
Latency graph
This is a bar graph that displays the average latency for the Destination across all Pipelines replicating data to it. The graph points denote latency at different points in time.
Here are a few things you can do to get the most out of your load graphs:
-
View the average and load-specific latency: Hevo displays the average latency for your Destination across multiple loads for the selected time duration. In addition to this, hovering over the bars displays the latency experienced in each Destination load. For example, in the image below, while the average latency over the last 2 hours is 40 sec 31 ms, the latency for the specific load is 41 sec 169 ms.
-
View latency for different durations: Hevo displays the latency for a default duration of 24 hours. The average latency changes depending on the duration you select. For example, the average latency is 1 min in the last 24 hours in the image below.