You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Analyzed 8 recent workflow runs from the last 7 days. Firewall coverage is complete across the 5 sampled firewall-enabled runs, and MCP telemetry is complete across the 8 sampled MCP-enabled runs. No critical observability gaps were found. All firewall runs had usable access.log output, and all MCP runs had rpc-messages.jsonl present as the canonical fallback.
Key Alerts and Anomalies
No critical issues detected.
Critical Issues:
None.
Warnings:
None.
gateway.jsonl was not present in the sampled MCP runs; rpc-messages.jsonl covered telemetry successfully in every case.
Missing MCP Telemetry (gateway.jsonl and rpc-messages.jsonl both absent): None in the sampled set.
Telemetry Quality Analysis
Firewall log quality:
Total access.log requests analyzed: 451
Unique allowed domains observed: 15
Blocked requests observed: 0
Sampled traffic was dominated by api.openai.com, gh-aw-foundry.openai.azure.com, api.anthropic.com, api.githubcopilot.com, github.com, and observability endpoints
MCP log quality:
Telemetry source: rpc-messages.jsonl in all sampled MCP runs
Average response time: N/A from this fallback source; gateway.jsonl was not emitted in the sampled runs
Healthy runs summary:
All sampled firewall-enabled runs had complete access.log coverage
All sampled MCP-enabled runs had usable telemetry via rpc-messages.jsonl
Recommended Actions
Keep access.log collection mandatory for firewall-enabled workflows.
Preserve rpc-messages.jsonl fallback until gateway.jsonl is emitted consistently.
If blocked-network debugging becomes important, add at least one intentionally blocked egress test to the sampling plan so firewall logs show both allowed and denied paths.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Caution
agentic threat detected
Threat detection flagged this output in warn mode. Manual review is REQUIRED before any follow-up automation.
Details
The threat detection engine failed to produce results.
Review the workflow run logs for details.
Executive Summary
Analyzed 8 recent workflow runs from the last 7 days. Firewall coverage is complete across the 5 sampled firewall-enabled runs, and MCP telemetry is complete across the 8 sampled MCP-enabled runs. No critical observability gaps were found. All firewall runs had usable
access.logoutput, and all MCP runs hadrpc-messages.jsonlpresent as the canonical fallback.Key Alerts and Anomalies
No critical issues detected.
Critical Issues:
Warnings:
gateway.jsonlwas not present in the sampled MCP runs;rpc-messages.jsonlcovered telemetry successfully in every case.Coverage Summary
access.log)gateway.jsonlorrpc-messages.jsonl)Detailed Run Analysis
Firewall-Enabled Runs
Missing Firewall Logs (
access.log): None in the sampled set.MCP-Enabled Runs
rpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlrpc-messages.jsonlMissing MCP Telemetry (
gateway.jsonlandrpc-messages.jsonlboth absent): None in the sampled set.Telemetry Quality Analysis
Firewall log quality:
access.logrequests analyzed: 451api.openai.com,gh-aw-foundry.openai.azure.com,api.anthropic.com,api.githubcopilot.com,github.com, and observability endpointsMCP log quality:
rpc-messages.jsonlin all sampled MCP runssafeoutputs,serena,mcpscripts,agenticworkflows,githubgateway.jsonlwas not emitted in the sampled runsHealthy runs summary:
access.logcoveragerpc-messages.jsonlRecommended Actions
access.logcollection mandatory for firewall-enabled workflows.rpc-messages.jsonlfallback untilgateway.jsonlis emitted consistently.References:
Report generated automatically by the Daily Observability Report workflow
Analysis window: Last 7 days | Runs analyzed: 8
Beta Was this translation helpful? Give feedback.
All reactions