Hello Folks,
I am currently reviewing and learning the NCM Compliance Job feature in SolarWinds and would appreciate some clarification regarding the report generation process. Based on the documentation, my understanding is that the workflow is as follows:
- Create Compliance Rules.
- Assign the Rules to a Policy.
- Add the Policy to a Compliance Report.
- Run the Compliance Job to generate compliance results.
While reviewing the compliance reports, I noticed that the Report Status is displayed as "Not Cached" for some reports.Could you please help me understand:
- What exactly does the "Not Cached" status indicate in the context of NCM Compliance Reports?
- How is a Not Cached report different from a Cached report?
- Does the status impact the compliance evaluation process or only the report display/generation?
- When generating a policy compliance report, are there any prerequisites or best practices related to report caching that we should be aware of?
- Can a report showing Not Cached still be considered the latest and valid compliance result?
@cnorborg @KMSigma.SWI @jeremymayfield
Regards,
Akash