Actors Monitoring

Under maintenance

Pricing

Pay per usage

Try for free

Go to Apify Store

Actors Monitoring

Under maintenance

Try for free

Developed by

Hamza Alwan

Maintained by Community

0.0 (0)

Pricing

Pay per usage

Last modified

a month ago

Automation

Report Mode

actorModeEnumRequired

Choose which type of report to generate.

Value options:

"compare": string"monthly": string

Default value of this property is "monthly"

Use Direct Actor Runs (Skip Tasks)

useDirectActorRunsbooleanOptional

If enabled, fetches runs directly from actors instead of going through tasks. This is useful for monitoring Actors without tasks.

Default value of this property is true

Email Recipients

emailRecipientsarrayOptional

List of email addresses to receive the generated reports.

Apify API Token

tokenstringOptional

Optional Apify API token. If not provided, will use the current user token.

Include Actors

actorNameIncludearrayOptional

Only process actors whose names contain any of these substrings.

Exclude Actors

actorNameExcludearrayOptional

Skip actors whose names contain any of these substrings.

Include Tasks (Ignored in useDirectActorRuns: true)

taskNameIncludearrayOptional

Only process tasks whose names contain any of these substrings. (Ignored when Direct Actor Runs is enabled)

Exclude Tasks (Ignored in useDirectActorRuns: true)

taskNameExcludearrayOptional

Skip tasks whose names contain any of these substrings. (Ignored when Direct Actor Runs is enabled)

Filter Runs by Status

filterRunsByStatusarrayOptional

Run statuses to filter by in monthly reports. If not provided, all statuses will be included.

Default value of this property is []

First Run ID (Comparison Mode)

compareRunId1stringOptional

Optional: Specific run ID for comparison. If both compareRunId1 and compareRunId2 are provided, these specific runs will be compared instead of fetching the most recent runs. Only used in compare mode.

Second Run ID (Comparison Mode)

compareRunId2stringOptional

Optional: Second specific run ID for comparison. If both compareRunId1 and compareRunId2 are provided, these specific runs will be compared instead of fetching the most recent runs. Only used in compare mode.

Field Comparison Strategies

fieldsAndCompareStrategyobjectOptional

🎯 Define Custom Comparison Strategies

Specify how each field should be compared between runs. If not provided, the system will use intelligent auto-detection.

📊 Available Strategies:

count - Compare number of items containing the field
sum - Compare total sum of all numeric values
average - Compare average of all numeric values
array_length - Compare total length of all arrays combined
coverage - Compare percentage of items that have this field populated

Default value of this property is {}

Combine Emails

combineEmailsbooleanOptional

When enabled, all comparisons are combined into a single email with one unified table. When disabled, each comparison is sent as a separate email.

Default value of this property is true

Email Only for Significant Changes - Compare Mode (5% Items Count Threshold)

notifyOnSignificantChangebooleanOptional

When enabled, comparison emails are only sent if the items count difference between runs exceeds 5%. This reduces noise from minor fluctuations in dataset sizes while ensuring you're notified of meaningful changes in data volume. Examples: 1,000 → 1,030 items (+3%): No email sent | 1,000 → 1,060 items (+6%): Email sent | 0 → any items: Always email sent.

Default value of this property is true

Custom Dimensions for Monthly Reports

customDimensionsarrayOptional

🎯 Custom Categorization Dimensions

Define custom dimensions for organizing runs in monthly reports beyond the default time-based categorization.

📋 Properties:

field - Path to extract values from run data (e.g. 'actorName', 'status', 'stats.runTimeSecs')
label - Display label for reports (optional)
fallback - Default value when field is missing (optional)

Months to Analyze

monthsToAnalyzeintegerOptional

Number of full calendar months to analyze for monthly reports. For example, 3 means the last 3 complete calendar months. Must be between 1 and 24 months.

Default value of this property is 3

Max Runs per Actor/Task

maxRunsintegerOptional

Maximum number of runs to analyze per actor or task in monthly reports. Higher values provide more comprehensive data but may increase processing time.

Default value of this property is 100

🎉 Apify Actors

prog-party/apify-actors

This Apify Actors Actor retrieves data from Apify, allowing to filter, and returns a list of actors as a Dataset.

Prog Party

Open Source Actors Scraper

lukaskrivka/open-source-actors-scraper

Get all open-source Actors from Apify Store.

Lukáš Křivka

Abort Actor Runs

mnmkng/abort-actor-runs

This actor enables the aborting of all user's running actors with a single click or by a single API call. Scans all actors of the user, aborts all RUNNING and READY actors. It is set to minimize compute unit usage at the expense of speed. Scans the user's actors sequentially to prevent API abuse.

Ondra Urban

Monitoring Runner

apify/monitoring-runner

The monitoring runner is a part of the Apify Monitoring Suite (apify/monitoring). See its readme for more information and how to use this.

Apify

135

4.5

Monitoring Checker Stats

apify/monitoring-checker-stats

The monitoring checker stats is a part of the Apify Monitoring Suite (apify/monitoring). See its readme for more information and how to use this.

Apify

4.8

Actor Build Starter

fjvs0283/actor-batch-builder

Run builds for multiple actors in your account simultaneously. This can be useful when many actors in a given project have been updated. For example, the documentation might have been updated in 50 actors. This tool will help you trigger actor builds for all 50 at once.

Francisco Villarreal

Monitoring Checker Run Status

apify/monitoring-checker-run-status

The monitoring checker run status is a part of the Apify Monitoring Suite (apify/monitoring). See its readme for more information and how to use this.

Apify

4.8

Monitoring Teardown

apify/monitoring-teardown

The monitoring teardown is a part of the Apify Monitoring Suite (apify/monitoring). See its readme for more information and how to use this.

Apify

5.0

Monitoring Checker Schema

apify/monitoring-checker-schema

The monitoring checker schema is a part of the Apify Monitoring Suite (apify/monitoring). See its readme for more information and how to use this.

Apify

4.8

Monitoring Reporter Slack

apify/monitoring-reporter-slack

The Monitoring reporter slack is a part of the Apify Monitoring Suite (apify/monitoring). See its readme for more information and how to use this.

Apify

4.1

Actors Monitoring

Actors Monitoring