Edge Device Error Analysis
Review and triage device error logs and exception traces captured across edge devices and gateways. SRE & DevOps engineers can submit diagnostic remarks.
Error Filters
GET /edge-devices/analysis
Presets:
Edge Device Error Records
0 records
Ordered: Incident Date (Latest first), Tenant, Device
| Tenant | Incident Date | Status | Resolved Date | Device Name | Title | Error Logs / Details | Remarks | Actions |
|---|---|---|---|---|---|---|---|---|
| Loading edge device error data... | ||||||||
GCP Cloud Asset Inventory
Aggregates downstream resources across projects and folder hierarchies. Automatically discovered and synchronized via Cloud Function (
Primary Target Folder:
idp-gcp-inventory-scanner) and reconciled with SCD Type 2 history in gcp_db.Primary Target Folder:
industrial-cloud.
Active Assets
0
tracked
Active Projects
0
projects
Folders
0
folders
Last Scan Status
IDLE
Never
Project Breakdown
Top 10 Projects
Regional & Location Distribution
Zones & Regions
Section 1: Release Health & Readiness Overview
Executive health status, scope completion rate, and ticket classification.
🟢
Calculating Release Health...
Reviewing delivery progress and unmerged code changes.
Scoped Stories
0
Scoped Repositories
0
Story Traceability Rate
0%
Total Code Commits
0
Leftover Risks
0
Delivery Status Breakdown
Consolidated
Issue Type & Priority Distribution
Jira Scope
Section 2: Team Workload, Velocity & Repository Distribution
Workload distribution across engineering squads and repository code impact.
Stories Delivered by Team
Per Squad
Commits by Repository
Code Churn
Team Performance & Delivery Matrix
Calculated Insights
| Team Squad | Total Stories | Completed Stories | Completion % | Bugs / Fixes | Linked Commits | Leftover Risks | Delivery Health |
|---|---|---|---|---|---|---|---|
| Loading team performance insights... | |||||||
Scoped Repositories Delivery Matrix
0 Repositories in Scope
| Repository | Scoped Stories | Merged Commits | Leftover Commits | Total Commits | Story Keys | Release Readiness Status |
|---|---|---|---|---|---|---|
| Loading repository delivery insights... | ||||||
Section 3: Risk Governance & Leftover Slippage Analysis
Audit of unmerged commits, orphaned Jira issues, and actionable remediation insights.
Leftover & Slippage Reasons
Leftover Commits & Jira
Release Quality Gate Evaluation
Analyzing leftover items and commit links...
High-Priority Risk Items & Remediation Plan
Actionable Items
| Item / Key | Type | Repository / Team | Summary / Description | Risk / Slippage Reason | Recommended Action |
|---|---|---|---|---|---|
| No high-risk leftover items detected. | |||||
Section 4: Story Deployment Notes & Readiness
Deployment instructions, pre/post rollout steps, and repository associations per story.
0 Stories
0 with Notes
Deployment Notes per Story
| Story Key | Repository | Scope | Team / Squad | Story Summary | Deployment Notes |
|---|---|---|---|---|---|
| Loading deployment notes per story... | |||||
Monitored Projects
0
in 0 subgroups
CI/CD Variables
0
managed secrets
Secret Masking
0%
0% protected
Branch Governance
0%
0 protected rules
Total Requests
0
audited
Pending Approval
0
awaiting devops
Approved & Executed
0
mutations
Approval Rate
100%
governance score
Distribution:
Loading distribution...
Sorted: Newest first
Change Requests
GET /api/request/change
Enterprise CUD Governance Pipeline: All infrastructure mutations (variables, branch protection, environments) are routed through Change Requests (
POST /api/request/change/create). Direct write APIs are restricted. Only users with the devops role can review, approve, and execute requests.
| ID | Requester | Request Type | Target Endpoint | Payload Summary | Status | Created At | Approver / Executed | Actions |
|---|---|---|---|---|---|---|---|---|
| Loading change requests from database... | ||||||||