🔍 Agentic Workflow Audit Report - November 18, 2025 #4240
Closed
Replies: 1 comment
-
|
This discussion was automatically closed because it was created by an agentic workflow more than 1 week ago. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
🔍 Agentic Workflow Audit Report - November 18, 2025
This audit covers workflow activity from the last 24 hours and provides trend analysis over the past 3 days. The audit analyzed 61 workflow runs with comprehensive error detection and performance metrics.
Audit Summary
Overall Health: 🟢 GOOD - 90.2% success rate
Performance Metrics
📈 Workflow Health Trends
Success/Failure Patterns
The workflow health has been consistently strong over the past 3 days with success rates ranging from 85-95%. The number of daily runs increased from 15 on Nov 16 to 28 on Nov 18, showing healthy activity levels. Failed runs remain minimal with only 1-2 failures per day, and cancellation rates are very low (0-2 per day).
Token Usage & Costs
Token consumption peaked on November 17 at approximately 9.3 million tokens ($6.93), then decreased to about 4.3 million tokens ($3.88) on November 18. The daily cost trend shows efficient resource usage with costs correlating directly to activity levels. The average cost per thousand tokens remains consistent at approximately $0.75-$0.80.
Full Analysis Details
Missing Tools
Status: ✅ No missing tools detected
No workflows reported missing tool requests during the audit period. All required tools were available and functional.
Error Analysis
Top Workflows by Error Count
The following workflows experienced the highest number of errors (note: many "errors" in the logs are actually informational JSON messages logged with error-level severity):
Error Pattern Analysis
Most detected "errors" fall into these categories:
JSON Message Logging: Many errors are actually structured JSON messages logged at error level, including:
Git Reference Resolution: Some workflows encountered Git reference resolution issues:
EventEmitter Memory Warnings: Node.js memory leak warnings in some workflows:
Exit Status Errors: Standard command exit status codes (e.g., "exit status 1")
Critical Errors
None identified - All workflows that failed did so gracefully with proper error reporting. No system-level failures or crashes detected.
Failed Workflow Runs
Three workflows failed during the audit period:
Documentation Unbloat - §19446157378
Unknown Workflow - Run ID not captured
Third Failed Run - Details to be investigated
MCP Server Failures
Status: ✅ No MCP server failures detected
All MCP servers (GitHub, safeoutputs, ast-grep) operated normally during the audit period.
Firewall Analysis
Summary: 4 total requests, all allowed (100% allowance rate)
Allowed Domains
api.enterprise.githubcopilot.com:443- 2 requestsapi.github.com:443- 1 requestregistry.npmjs.org:443- 1 requestDenied Domains
None - all network requests were properly authorized.
Firewall Activity by Workflow
The firewall is functioning correctly with appropriate domain allowlisting. No suspicious or unauthorized network access attempts detected.
Tool Usage Statistics
Most frequently used tools across all workflows:
Affected Workflows
✅ Healthy Workflows (95% success or better)
Recommendations
High Priority
Investigate Documentation Unbloat Failure
Review Error Logging Practices
Medium Priority
Address EventEmitter Warnings
emitter.setMaxListeners()calls where neededMonitor Token Usage Trends
Low Priority
Historical Context
This is the second audit in the index. Comparing with previous audits:
Next Steps
References:
Beta Was this translation helpful? Give feedback.
All reactions