Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compliance Data Aggregation Cadences | Client Side and Central View #367

Closed
MathesonSho opened this issue Jan 16, 2025 · 0 comments · Fixed by #373
Closed

Compliance Data Aggregation Cadences | Client Side and Central View #367

MathesonSho opened this issue Jan 16, 2025 · 0 comments · Fixed by #373
Assignees
Labels
enhancement New feature or request Iteration #1 Before V2.0 go-live

Comments

@MathesonSho
Copy link
Contributor

Azure CaC current version
v2.1.5

Is your feature request related to a problem? Please describe.
Currently the clients solution runs every 6 hours from when the solution was installed. Moving forward this collection on the client side is only needed once per day.

Further the central aggregation of client side reports is also needed once per day.

Describe the solution you'd like
Could we modify the runbook to collect data on the client side at a specific time. For example 2AM ET each day.

Could we modify the centralreporting view aggregation to collect data on the enterprise side at a specific time. For example 5AM ET each day.

Describe alternatives you've considered

  • specific time once per day
  • set the cadence to every 24 hours (least preferred)
@MathesonSho MathesonSho added enhancement New feature or request Iteration #1 Before V2.0 go-live labels Jan 16, 2025
@dutt0 dutt0 self-assigned this Jan 17, 2025
@dutt0 dutt0 linked a pull request Jan 23, 2025 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Iteration #1 Before V2.0 go-live
Projects
None yet
2 participants