humio/activity Dashboards
Alert Details
Widget | Description | Type |
---|---|---|
Overview of problems with the alert.
logscale
| Table | |
Shows the status of the alert within the last minute. If the alert
was successfully polled, it is green. Otherwise, if the alert had
a failure, it is red. Otherwise, if the alert had a success, it is
green. Otherwise, the alert is grey.
logscale
| Single Value | |
This chart displays when the alert successfully triggered.
logscale
| Time Chart | |
Shows the status of the alert over time.
logscale
| Time Chart | |
Shows whether the filter or aggregate alert is running historic
queries to catch up over time. Note: Legacy alerts do not run
historic queries to catch up.
logscale
| Time Chart | |
Whether the filter or aggregate alert is running historic queries
to catch up and not reacting to new events in the meantime. Note:
Legacy alerts do not run historic queries to catch up.
logscale
| Single Value | |
parameterPanel |
Alerts Overview
Widget | Description | Type |
---|---|---|
Displays a table of alert problems (repository, alert name, last
failed, last severity, etc.)
logscale
| Table | |
This chart displays how many distinct aggregate or filter alerts
over time per repository/view are running historic queries to
catch up and not reacting to new events in the meantime. Note:
Legacy alerts do not run historic queries to catch up.
logscale
| Time Chart | |
Overview of alerts that triggered and successfully invoked at
least one action.
logscale
| Table | |
This chart displays how many distinct alerts triggered over time
per repository or view.
logscale
| Time Chart | |
Overview over aggregate or filter alerts that are running historic
queries to catch up and not reacting to new events in the
meantime. Note: Legacy alerts do not run historic queries to catch
up.
logscale
| Table | |
This chart displays how many distinct alerts had problems over
time per repository or view.
logscale
| Time Chart | |
Select problem severities and categories to show. | parameterPanel |
FDR Ingest Status
Widget | Description | Type |
---|---|---|
How many distinct FDR feeds had problems per repository.
logscale
| Time Chart | |
Number of error or warning logs per feed as well as the number of
restarts. Unless the feed configuration is changed, a restart
suggests some sort of problem with the feed. Also shows
information about the last problem.
logscale
| Table | |
SQS messages that failed and have not yet been successfully
retried.
logscale
| Table |
Filter Alert Details
Widget | Description | Type |
---|---|---|
Shows whether the filter alert is running historic queries to
catch up over time.
logscale
| Time Chart | |
Whether the filter alert is running historic queries to catch up
and not reacting to new events in the meantime.
logscale
| Single Value | |
Overview of warnings with the filter alert.
logscale
| Table | |
This chart displays when the alert successfully triggered.
logscale
| Time Chart | |
Number of error or warning logs per feed as well as the number of
restarts. Unless the feed configuration is changed, a restart
suggests some sort of problem with the feed. Also shows
information about the last problem.
logscale
| Table | |
Shows the status of the alert within the last minute. If the alert
was successfully polled, it is green. Otherwise, if the alert had
a failure, it is red. Otherwise, if the alert had a success, it is
green. Otherwise, the alert is grey.
logscale
| Single Value | |
Shows the status of the alert over time.
logscale
| Time Chart |
Filter Alerts Overview
Widget | Description | Type |
---|---|---|
How many distinct FDR feeds had problems per repository.
logscale
| Time Chart | |
Overview of errors with invoking actions when a filter alert
triggers.
logscale
| Table | |
Overview of errors with running filter alerts due to either the
user having been deleted or the user not having permissions to run
the filter alert. Fix this by either granting the user the missing
permissions, change the alert to run as another user, or change
the alert to run on behalf of the organization.
logscale
| Table | |
Overview of other errors with running filter alerts than the three
lists above.
logscale
| Table | |
Overview of warnings with invoking actions when a filter alert
triggers. Note that if the filter alert has multiple actions
attached and at least one succeeds, it is considered to have
triggered.
logscale
| Table | |
This chart displays when the alert successfully triggered.
logscale
| Time Chart | |
Number of error or warning logs per feed as well as the number of
restarts. Unless the feed configuration is changed, a restart
suggests some sort of problem with the feed. Also shows
information about the last problem.
logscale
| Table | |
This chart displays how many distinct filter alerts over time per
repository/view are running historic queries to catch up and not
reacting to new events in the meantime.
logscale
| Time Chart | |
Overview over filter alerts that are running historic queries to
catch up and not reacting to new events in the meantime.
logscale
| Table | |
This chart displays how many distinct filter alerts had warnings
over time per repository or view.
logscale
| Time Chart | |
Overview of filter alerts that triggered and successfully invoked
at least one action.
logscale
| Table | |
Overview of warnings with running the filter alert queries.
logscale
| Table | |
Overview of errors with running filter alert queries. This can
either be due to an error in the query or due to problems in the
cluster causing errors when trying to run the query.
logscale
| Table |
Legacy Alert Details
Widget | Description | Type |
---|---|---|
This chart displays when the alert successfully triggered.
logscale
| Time Chart | |
Shows how many times the legacy alert query was restarted over
time. If this happens more than a few times, it could indicate
that the query is getting killed or has another problem.
logscale
| Time Chart | |
Number of error or warning logs per feed as well as the number of
restarts. Unless the feed configuration is changed, a restart
suggests some sort of problem with the feed. Also shows
information about the last problem.
logscale
| Table | |
Shows the status of the alert within the last minute. If the alert
was successfully polled, it is green. Otherwise, if the alert had
a failure, it is red. Otherwise, if the alert had a success, it is
green. Otherwise, the alert is grey.
logscale
| Single Value | |
Shows the status of the alert over time.
logscale
| Time Chart |
Legacy Alerts Overview
Widget | Description | Type |
---|---|---|
How many distinct FDR feeds had problems per repository.
logscale
| Time Chart | |
Overview of errors with invoking actions when a filter alert
triggers.
logscale
| Table | |
Overview of errors with running filter alerts due to either the
user having been deleted or the user not having permissions to run
the filter alert. Fix this by either granting the user the missing
permissions, change the alert to run as another user, or change
the alert to run on behalf of the organization.
logscale
| Table | |
This chart displays when the alert successfully triggered.
logscale
| Time Chart | |
Shows how many times the legacy alert query was restarted over
time. If this happens more than a few times, it could indicate
that the query is getting killed or has another problem.
logscale
| Time Chart | |
Number of error or warning logs per feed as well as the number of
restarts. Unless the feed configuration is changed, a restart
suggests some sort of problem with the feed. Also shows
information about the last problem.
logscale
| Table | |
Lists all the times legacy alert queries restarted in time
descending order. No. of times restarted represents how many times
the query has restarted in the search window. If this number is
high, it could indicate that the query is getting killed or has
another problem.
logscale
| Table | |
Overview of filter alerts that triggered and successfully invoked
at least one action.
logscale
| Table |
Scheduled Reports Overview
Widget | Description | Type |
---|---|---|
How many distinct FDR feeds had problems per repository.
logscale
| Time Chart | |
Overview of warnings related to scheduled reports.
logscale
| Table | |
Overview of errors with invoking actions when a filter alert
triggers.
logscale
| Table | |
Overview of scheduled reports which cannot keep up with the
schedule and where a planned execution was skipped. Scheduled
reports that are on this list should first be checked if they have
other problems. Second, if the time they lagged behind was a time
where LogScale was not running optimally. If neither is the case,
the target dashboard might need to be optimized.
logscale
| Table | |
There is a limit to the size of pdf files LogScale will send. This
widget shows a number of too large pdf reports that have been
generated and attempted sent.
logscale
| Single Value | |
This chart displays when the alert successfully triggered.
logscale
| Time Chart | |
Number of error or warning logs per feed as well as the number of
restarts. Unless the feed configuration is changed, a restart
suggests some sort of problem with the feed. Also shows
information about the last problem.
logscale
| Table | |
Overview of errors related to scheduled reports.
logscale
| Table | |
Overview of the time it takes for a report to transition from
being planned to completing either as a success with the email
being sent or a failure.
logscale
| Time Chart | |
Overview of filter alerts that triggered and successfully invoked
at least one action.
logscale
| Table |
Scheduled Search Details
Widget | Description | Type |
---|---|---|
This chart displays when the alert successfully triggered.
logscale
| Time Chart | |
Number of error or warning logs per feed as well as the number of
restarts. Unless the feed configuration is changed, a restart
suggests some sort of problem with the feed. Also shows
information about the last problem.
logscale
| Table | |
Shows the status of the alert over time.
logscale
| Time Chart |
Scheduled Searches Overview
Widget | Description | Type |
---|---|---|
How many distinct FDR feeds had problems per repository.
logscale
| Time Chart | |
Overview of errors with invoking actions when a filter alert
triggers.
logscale
| Table | |
Overview of scheduled reports which cannot keep up with the
schedule and where a planned execution was skipped. Scheduled
reports that are on this list should first be checked if they have
other problems. Second, if the time they lagged behind was a time
where LogScale was not running optimally. If neither is the case,
the target dashboard might need to be optimized.
logscale
| Table | |
Overview of errors with running filter alerts due to either the
user having been deleted or the user not having permissions to run
the filter alert. Fix this by either granting the user the missing
permissions, change the alert to run as another user, or change
the alert to run on behalf of the organization.
logscale
| Table | |
This chart displays when the alert successfully triggered.
logscale
| Time Chart | |
Number of error or warning logs per feed as well as the number of
restarts. Unless the feed configuration is changed, a restart
suggests some sort of problem with the feed. Also shows
information about the last problem.
logscale
| Table | |
Overview of filter alerts that triggered and successfully invoked
at least one action.
logscale
| Table |