Activeboard: Devo Collector Monitoring

[ 1 Purpose ] [ 2 Included widgets ] [ 3 Prerequisites ] [ 4 Open Activeboard ] [ 5 Use Activeboard ]

Purpose

This Activeboard keeps you updated about everything that happens within your collectors. From regular activity to critical errors, nothing gets past you.

The primary focus of Activeboard lies in detecting malfunctioning collectors during the monitoring of operational collectors. It also plays a crucial role in pinpointing credential issues (401 and 403) and server errors (501 and 503). This Activeboard also provides valuable insights into regular activities, helping to ensure that all operations are running smoothly.

The Activeboard is configured to show data for the last month by default. This provides ample context to ascertain the actual status of the collectors and address issues where necessary. Once you spot where the problems are, you can use the Go to query option to examine the data in detail.

This Activeboard complements the Alert Pack Collector, so we highly recommend using them in combination.

Included widgets

Collectors Monitoring (overview)
Total collectors (Simple value): it shows the number of active collectors in the domain.	Collectors not sending data last 60m (Table widget): whenever a collector stops processing data for 60 minutes, the last data processing is recorded and displayed here. This does not necessarily implies an error, but it’s worth observing nonetheless.
Failing collectors (Simple value): it shows the number of inactive collectors in the domain.	Failed collectors messages (Table widget): whenever a collector ceases operations, the details are recorded and displayed here.
Errors & Warnings by collectors (Voronoi widget): it shows activity that deviates from optimal functioning, either with successful or unsuccessful results. This assists in identifying the most susceptible collectors, enabling you to foresee and prioritize effectively.	Errors by collectors (Voronoi widget): it only shows activity that entails unsuccessful functioning. This assists you in identifying the most vulnerable collectors, allowing you to act promptly where it’s most needed.
Section 1 - Collectors Activity
Collector activity (Line chart): it displays the number of actions detected across all collectors over time, enabling you to identify patterns and potential downtimes.
Type of messages (Pie chart): it shows activity classified by type (info, warning, error…), allowing you to assess the overall stability of the collector environment.	Type of errors (Pie chart): it shows errors classified by type or code, allowing you to assess at a glance the severity of the errors encountered.
Section 2 - Credential errors
Errors & Warnings 401/403 by Collector (Line chart): it displays the number of 401/403 errors and warnings detected across all collectors over time, enabling you to identify patterns and significant spikes of credential errors. You can use the Go to query option to examine the specific errors and warnings in detail.	Errors & Warnings 401/403 by Collector (Table widget): it displays the total number of 401/403 errors and warnings detected in each collector, enabling you to easily identify where credential problems occur and their significance. You can use the Go to query option to examine the specific errors and warnings in detail.
Section 3 - API Limits errors
Errors & Warnings 429 by collector (Line chart): it displays the number of 429 errors detected across all collectors over time, enabling you to identify patterns and significant spikes of limit errors.	Errors & Warnings 429 by Collector (Table widget): it displays the total number of 429 errors detected in each collector, enabling you to easily identify where limit problems occur and their significance.
Section 4 - Server errors
Errors & Warns 500 "Internal Server Error" by collector (Line chart): it displays the number of 500 errors detected across all collectors over time, enabling you to identify patterns and significant spikes of internal server errors.	Errors & Warns 50x by Collector (Table widget): it displays the total number of 500 errors of any kind detected in each collector, enabling you to easily identify where server problems occur and their significance.
Errors 503 "Service Unavailable" by collector (Line chart): it displays the number of 503 errors detected across all collectors over time, enabling you to identify patterns and significant spikes of service unavailability.	Errors 501 "Not implemented" by collector (Line chart): it displays the number of 501 errors detected across all collectors over time, enabling you to identify patterns and significant spikes of implementation issues.

Prerequisites

To use this Activeboard, you must have the following data sources available in your domain:

devo.collectors.out

Open Activeboard

Once you have installed the Activeboard, you can use the Open button at the top right of the card in Exchange to access it and see the different widgets populated with the relevant data. You can also access the Activeboard area via the Navigation pane.

Data loading takes too long?

Sometimes some widgets take time to upload the data, it is possible to speed up the process by creating aggregation tasks. Refer to the Aggregation tasks article to learn how to do it.

Use Activeboard

After installing and opening the Activeboard, you can use its widgets to visualize and monitor data. To do this, each widget offers a variety of customization and visualization options. Refer to Using widgets and Using inputs to know them all.