Navigate to the standard Reports tab where you will find a report folder titled File Slayer Reports, and three packaged reports: File Slayer Usage This Year (Size), File Slayer Usage This Year (Count), and Slaybot vs. Component Slaying. 

Please note, if you installed File Slayer before version 3.30, you may have legacy reports Slayer Totals and Images Slayed by Use in addition. These reports have been deprecated and the related fields no longer contain accurate File Slayer metrics.

Starting in version 3.30, File Slayer no longer relies on previously packaged Case fields to calculate File Slayer metrics. Now, we will be leveraging the File Slayer Usage Object, which allows File Slayer to calculate files slain in all standard and custom objects to give greater insight into which method a file is slain. 

Here are the items that File Slayer Usage records can calculate: 

• Monthly record of the user who slayed files 
• Files Added to the Blocked List: Total count of files added to the Blocked List 
• Files Slain via Slaybot (Count): Total count of files slain by Slaybot 
• Files Slain via Slaybot (Size): Total size of files slain by Slaybot 
• Files Slain via File Library (Count): Total count of files slain manually via the Hit List Manager 
• Files Slain via File Library (Size): Total size of files slain manually via the Hit List Manager 
• Files Slain via Component (Count): Total count of files slain manually via the File Slayer lightning component
• Files Slain via Component (Size): Total size of files slain manually via the File Slayer lightning component
• Slain Automatically via Checksum (Count): Total count of files slain via existing checksum on the blocked list (For example, if you slay a Facebook icon and the same Facebook icon tries to enter the org, it will be automatically removed and counted in this bucket) 
• Slain Automatically via Checksum (Size): Total count of files slain via existing checksum on the blocked list (For example, if you slay a Facebook icon and the same Facebook icon tries to enter the org, it will be automatically removed, and the size of that file is counted in this bucket) 
• Files Slain Retroactively (Count): Total count of files slain automatically in a retroactive removal batch (setting must be enabled) 
• Files Slain Retroactively (Size): Total size of files slain automatically in a retroactive removal batch (setting must be enabled) 
• Duplicate Files Deleted (Count): Total count of files slain as a duplicate when the duplicate file is detected on the same record (setting must be enabled)
• Duplicate Files Deleted (Size): Total size of files slain as a duplicate when the duplicate file is detected on the same record (setting must be enabled)
• Files Slain Total (Count): Total count of files slain
• Files Slain Total (Size): Total size of files slain

We have also packaged three reports to help organize this data in a meaningful way. You can edit these reports to your specific needs.

File Slayer Usage This Year (Size):

File Slayer Usage This Year (Count):

Slaybot vs. Component Slaying:

Please note that these sample reports are provided as-is, and customization is not supported. Further customization can be performed by your Salesforce Administrator or Consulting Partner.