Monitor events overview

Get an overview of Monitor events in Productsup.

To automatically inform you about the status of your data, Productsup offers extensive monitoring options. Monitor lets you stay fully informed at all times. This can help you understand how the processing of your data from import to export is running, or if there are errors that need attention.

This document is designed to provide you with in-depth information about the different monitoring events.

Note

  • Only Administrators or Users with Read/Write access are able to manage monitoring.

  • Make sure you have defined a Product Identifier in Data Sources.

Setting events to monitor

You can reach Monitor from site, project, and account level.

monitor_tab.png

In Monitor, Productsup offers over 25 different monitoring events, which are grouped into four (4) stages:

Monitoring event stages
  • import

  • intermediate

  • export

  • general

You can take a deeper look into what each event does and when it could be useful.

Tip

Some of the following events can be configured to have a threshold. This means that the event will only be triggered upon reaching a predetermined level (threshold). This is normally a percentage.

Monitoring on the import

All the monitoring events under this stage deal with the importing of your data into Productsup.

Monitoring Event

Description

Number of Imports without a change in Data Sources

A data source has not changed in a given number of runs. This could indicate that the process to update the files is broken, the URL is outdated, or your products are not being updated in the back-end.

New attribute added to Data Sources

A new attribute has been added to one of the data sources. This can help notify you that you need to check on your mapping.

Mapped attribute has been removed from Data Sources

An attribute has been removed from one of the data sources. This could indicate a misconfiguration on either the file creation on source side. You should check your files and your mapping.

Import file failed to download

Downloading your main feed from a data source was unsuccessful. You should check that the URL is valid, that authentication settings are correct, and that there are no technical issues on your side.

Import file is empty

An import file was downloaded, but did not contain any data. You should check whether there was a misconfiguration on your end whilst creating the file to send to Productsup.

Number of imported items decreased

The number of imported items has decreased compared to the last import. Big drops might indicate an issue, such as a misconfiguration of the original file or an issue with your back-end where you host the products. A big drop in products may delete many of your products from your feeds.

Item Identifier attribute disappeared

The attribute assigned as an product identifier in the Data Sources page has disappeared. This indicates that the attribute has been removed from the data sources, and could lead to failures in product uniqueness or in data services.

Number of import file download retries

You can set a given number of attempts the platform tries to download a file if the previous download attempts were unsuccessful. This is best used if the connection to a data source is known as unstable.

Monitoring on the intermediate

All of the events under this stage deal with your products as they are processed in the intermediate stage. They can help you monitor general changes in your data, such as large percentages of deleted products.

Monitoring Event

Description

Percentage of modified items

A given percentage of items between the import stage and the intermediate stage have been modified in comparison to the previous run. These modifications could due to a change in data directly in the data source, or have been applied either through rules in Productsup.

Percentage of added items

A given percentage of new products have been added to the feed, compared to the previous run.

Percentage of deleted items

A given percentage of products have been removed from the feed, compared to the previous run.

Monitoring on the export

All of the monitoring events under this stage deal with the exporting of your data. These events can help you set up monitoring for your feeds.

Monitoring Event

Description

Percentage of modified items in a delta export

A given percentage of items in a delta export have been modified in comparison to the previous run. These modifications could be coming directly from your data source, or through rules set in Productsup.

Percentage of added items in a delta export

A given percentage of new products have been added to the delta export, compared to the previous run.

Percentage of deleted items in a delta export

A given percentage of new products have been deleted from the delta export, compared to the previous run. These items have been removed from the feed completely or have been skipped.

Percentage of missing values in all mandatory attributes

A given percentage of products are missing values for mandatory attributes. These mandatory attributes are required by the export channels to be present in your feed.

Percentage of missing values in all optional attributes

A given percentage of products are missing values for optional attributes. These optional attributes are recommended by the export channels to be present in your feed.

Percentage of values in all mandatory attributes that failed a set Analyzer test

A given percentage of products failed an analyzer test for a mandatory attribute. This means that a product may be rejected by the export channel as the data is not conforming to the specifications they require.

Percentage of values in all optional attributes that failed a set Analyzer test

A given percentage of products failed an analyzer test for an optional attribute.

Feed upload failed

The upload of a feed failed and the export channel can not collect your file. It could be that an export destination was not reachable or that credentials have changed.

Fewer items exported

Fewer items have been exported compared to the last export. This could be due to fewer items being imported, or due to skip rules / ROI rules which have been applied.

More items exported

More items have been exported compared to the last export. This could be due to more items being imported, or due to skip rules / ROI rules which had been applied to the previous run and are not active anymore.

Monitoring the entire process (general)

General events monitor the entire processing of a site, from import through to export.

Monitoring Event

Description

Site run exceeds given number of hours

The run (link to glossary) has lasted longer than the given threshold. This could be due to a number of reasons such as the amount of products, or the optimization rules set.

Example of when to use Site run exceeds given number of hours:

Let’s say you are running your site once an hour and that this site normally takes 15 minutes to process. If there is a one-off occurrence where the site takes longer than one hour, then the next run will be queued and your data may not be updated in time for your exports.

In this case, you could set up the site run exceeds a given number of hours event to trigger an email and also stop the processing of this run, meaning that your normal schedule of one run per hour can continue to be met.

Setting up monitoring for every single site could be very time-consuming, especially if you want to set up the same events for each site.

As well as directly on the site level, you also have the option to set up overarching monitoring which applies to multiple sites or projects.

  • if you set up account level monitoring, this will apply across all projects and all sites in your account

  • if you set up project-level monitoring, this will apply across all sites in the project

  • if you set up site-level monitoring, this will apply only to the relevant site.

Using hierarchies in monitoring to specialized events

When setting up monitoring, it could be that you want to specialize a certain event for a certain project, site, or even export. For example, the monitoring over your entire account could not be strict enough for one site.

You can override a monitoring event by adding one on a lower level. A more granular/specialized monitoring event (i.e. one on a “lower-level”) will always take priority over a more general one. The settings of the monitoring event are not taken into account here.

  • Site settings take precedence over project settings

  • Site settings take precedence over account settings

  • Project settings take precedence over account settings

For exports, you have the option to define whether you monitor all export, specific export templates, or specific export channels.

  • Specific export templates settings take precedence over all exports settings on the site level

  • Specific export templates settings take precedence over all exports in project and account settings

  • Specific export channels settings take precedence over specific export templates settings

As a helpful reminder, you can see that the monitoring event which takes priority is shown in white, whilst all other overwritten monitoring events are grayed out. For the other sites in the project where we do not have this specialized event on-site level, you will only see the project monitoring event.

An example of where a site level monitoring is overwriting project level monitoring

An example of where site-level monitoring is overwriting project-level monitoring