Supplementing Health Check reports

You can create additional custom reports that supplement the Health Check reports included with your Medallia Experience Cloud solution. This topic includes information about using custom reports to monitor the health of your imports and exports for Web feeds and OmiExporters.

For detailed information about creating custom report modules, see Custom Module.

As a best practice, create a report to monitor every process you create. (The report can be internal only.) You can choose to allow customer administrators to view the reports, which is a good way to share processing statistics without sending emails.

Custom report templates

Experience Cloud includes several custom report templates you can use to get started. For Web feeds, use any of the following templates:

[SAMPLE HEALTH] Imported Files
[SAMPLE HEALTH] Incoming Web Feeds
[SAMPLE HEALTH] Processing Results Over Time
[SAMPLE HEALTH] Processed Files by Feed Over Time

For OmiExporters, use any of the following templates:

[EXPORT HEALTH] Exported Files
[EXPORT HEALTH] Exported Record Count Over Time
[EXPORT HEALTH] OmniExporter Event Overview
[EXPORT HEALTH] OmniExporter Events (Hour by Hour)

Report types

Three report types show data from different sources so you cannot combine data for exports, imports, and OmniExporters in a single report. Use one of the following values for the type attribute of the survey-type element in your report:

SURVEY_EXPORT_STATS — For file exports.
OMNI_EXPORTER_STATS — For OmniExporter data.
FEED_FILE_PROCESSING_REPORT — For imports of Web feeds.

Because each feed file (or hour of activity for Web feeds and OmniExporter) is stored as a survey record, Experience Cloud does not capture survey-level data (such as unit data and survey segment fields). Therefore, you cannot split by, filter by, or display survey level data in these reports.

Web feed and OmniExporter traffic is aggregated over the hour, so each data point in these reports represents an hour’s worth of traffic.

Splits

You can limit the reports by different attributes (processing-level A-fields). Search for “File Processing” or “Export” on the A-fields page to see all the available fields for monitoring import and exports events to display. Consider the following categories for your splits:

Feed account — For example, a_feed_file_processing_report_feed_account. For imports, you might want to consider only one feed pull: SFTP, or FTP.
Feed account type — For example, a_feed_file_processing_report_feed_account_type or a_survey_export_exported_via. You might want to consider only Feed Pulls vs. SFTPs, or only exports via FTP.
File status — For example, a_feed_file_processing_report_status or a_survey_export_status. You might want to consider only successful or unsuccessful processing.
Name — For example, a_survey_export_name or a_omni_exporter_name. You might want to cnsider only a particular set of imports, exports, or OmniExporter events.