Usage analytics
Introduction
The Usage analytics area displays metrics and charts that provide Admin users with insights into the health, status, and usage of the Devo platform. This way, Admins can easily check how their domains are being used.
You can access the Usage analytics area in Administration → Usage analytics.
What permissions do I need?
In order to access the Usage analytics area, you need to have a role with the the Usage analytics permission assigned. Learn more about role permissions in this article.
Overview tab
When you access the Usage analytics area, you will access the Overview tab, where you can see a series of informative figures at the top area:
Weekly active users | Number of unique active users in the domain during the last week. |
---|---|
Average daily ingestion volume | Average daily ingestion volume during the last week. |
Data search query count | Number of queries performed in the Data Search area yesterday. |
API query count | Number of queries performed using the Query API yesterday. |
OData query count | Number of OData feeds created yesterday. |
The rest of the page is divided into 4 different sections:
Ingestion per technology
This graph shows the daily ingestion volume during the last 7 days. For each day, you can see the technologies (data tables) that received data, and the percentage they represent in the total volume of that day.
Hover over each column to check the complete list of technologies that received data that date, along with their data volume and percentage. Hover over a specific section to highlight it on the window that appears.
You can also highlight the sections representing a specific technology in the graph by clicking it on the list at the right side.
Queries by type
This line chart represents the number of queries performed during the last 7 days, divided by type. This chart excludes queries from background processes like alerts, injections, query lookups and aggregations. Only UI queries and API queries are considered.
Hover over a line on the graph to check the specific number of queries of that type at a specific time. You can also highlight a specific type of query by hovering over the list at the bottom of the chart.
Resource usage distribution by component and time
This chart shows how the different areas of the Devo application consumed compute resources over the last 7 days.
Hover over a line on the graph to check the resources consumed by each area at a specific time. You can also highlight a specific Devo area by hovering over the list at the bottom of the chart.
Resource usage distribution by component
Similarly to the previous one, this pie chart represents which Devo areas have consumed more resources during the last 24 hours.
Hover over the slices of the pie to check the specific volume of resources used by each component. You can also hover over the component list to highlight the corresponding slices.
Background processes tab
In the Background processes tab, you will see a series of informative panels at the top area:
Alerts running | Number of alerts running in the domain over the last 24 hours. |
---|---|
Injections running | Number of injections running in the domain over the last 24 hours. |
Aggregation tasks running | Number of aggregation tasks running in the domain over the last 24 hours. |
Query lookups running | Number of query lookups running in the domain over the last 24 hours. |
Alerts failing | Number of alerts that failed in the domain over the last 24 hours. |
Injections failing | Number of injections that failed in the domain over the last 24 hours. |
Aggregation tasks failing | Number of aggregation tasks that failed in the domain over the last 24 hours. |
Query lookups failing | Number of query lookups that failed in the domain over the last 24 hours. |
Processes with errors in the query engine
At the bottom of this area, you will find a series of tables that inform about processes related to errors in the query engine. Each table shows details about resources failing in your domain: alerts, injections, aggregation tasks and query lookups.
You can check the name of the failing resource, the type of errors occurring and the count of alerts triggered.
Error codes
Check this article to understand the error codes in these tables.
Â
Â
Â
Â