As DMARC has become more widely adopted you will inevitably see an increase in DMARC reports. I cannot stress highly enough that you want DMARC reports to go to a unique address that is used only for collecting DMARC reports (i.e. firstname.lastname@example.org). That said, unless you are using a 3rd Party utility to parse DMARC reports (we used to use DMARC Analyzer but there are many other solutions) then after a period of time when you are certain that all emails from a domain are passing DMARC (30 days is usually ample enough time) you would want to set the policy (p= modifier) from "none" to either "quarantine" or "reject". This will dramatically reduce the number of DMARC reports you receive considerably as only those emails that fail will result in a DMARC report being sent (a p="none" will result in a DMARC report for passes and fails).
It is important to periodically review or audit these DMARC reports (which is why using a 3rd Party monitoring tool is useful). Most failures will be caused by Spoofed emails but invariably you'll have customers who will get a new network printer that they don't setup SMTP Authentication for, or will sign-up for QuickBooks or a Marketing Service such as Constant Contact or MailChimp which will cause emails from their domain to no longer be aligned with their SPF Records or using DKIM. To resolve these issues you would have to update their SPF or DMARC policies accordingly.
However, as long as you have p=none in your DMARC policy and the policy_evaluated and auth_results show "Pass" for both SPF and DKIM then you can safely ignore that report (and if a domain routinely gets passing marks then you can safely set your DMARC p= to a more restrictive modifier).