Analytics and reporting using the DevOps Config Insights dashboard
Summarize
Summary of Analytics and Reporting Using the DevOps Config Insights Dashboard
The DevOps Config Insights dashboard, integrated with Performance Analytics, enables users to quickly identify configuration errors and take necessary actions. It provides insights into snapshot validation trends, open changesets, and failed snapshots across all applications and deployables. Note that with the Washington DC release, DevOps Config will be deprecated in the future but will remain supported.
Show less
Key Features
- Configurable Error Thresholds: Users can set thresholds for errors according to their needs.
- Customizable Widgets: Widgets can be rearranged or hidden to suit user preferences.
- Filtering Options: Results can be filtered based on applications, deployables, and date.
Key Outcomes
- Open Changesets: DevOps engineers can review and manage open changesets to prevent them from becoming stale, minimizing data model risks.
- Failed Snapshots: Users are able to assess non-compliant snapshots to ensure adherence to company policies before production deployment.
- Policy Exceptions: Active exceptions can be monitored, and recommended actions for upcoming expirations can be identified.
Overall, the dashboard assists in maintaining configuration integrity and compliance, thereby enhancing operational efficiency. Users should aim for a zero count in open changesets and failed snapshots for optimal performance.
Use the DevOps Config Insights dashboard with Performance Analytics to quickly identify configuration errors and take action. View snapshot validation trend, open changesets, and failed snaphots for all applications and deployables.
Error thresholds are configurable and widgets are customizable (you can rearrange or hide them).
You can filter results on applications, deployables, and by date.
| Report | Description and use case |
|---|---|
| Open changesets | Open changeset details. Use case: As a DevOps engineer or App Engineer, I want to review my open changesets so that I can take action on them right away and not let them get stale. Accidentally committing changesets later could add risk to my data model and, by consequence, the fleet. |
| Failed snapshots | Non-compliant snapshots for changes committed. Use case: As a DevOps engineer or App Engineer, I want to review non-compliant snapshots for changes I committed so that I ensure my changes are in line with company policies before pushing the data out to my production environment. |
| Policy exception and recommended actions | Recommended actions for policies that have exceptions. Use case: As a DevOps Config and GRC customer, I want to be able to see the list of active exceptions and, for ones that are expiring soon, what the recommended action is. |
DevOps Config Insights Open changesets
Review the changeset details and either make changes to the config data and commit the changeset, or discard the changeset altogether. You generally want this number to be 0 on the dashboard.
DevOps Config Insights Failed snapshots
Investigate the snapshots and fix misconfigurations, or identify changes that need to be made to a policy. You generally want this number to be 0 on the dashboard.
DevOps Config Policy exceptions
| Nothing | If the issue is already resolved and the latest snapshot status passed; or withdraw the exception if it is no longer needed. |
| Fix the issue | If the latest snapshot validation status is passed with exception and there's time to fix the issue before the exception expires. |
| Extend the exception | If the latest snapshot validation status is passed with exception and there isn't enough time to fix the issue. |