Skip to content

Telemetry events

Your customer-stack’s Function App has an Application Insights component named pocai-ai-{stack-hash} in your subscription. You own it. We don’t have access. The data stays in your tenant.

What’s instrumented

  • Function App host telemetry — startup, function executions, durations, exception types. Standard.
  • Outbound HTTP — calls to your Cosmos, Azure OpenAI, SignalR, and the two ISV endpoints (deploy-status, seat-report).
  • Structured log lines[mail], [notify], [graph], [patcher] prefixes.

What’s NOT logged (enforced)

The no-content-egress rule (a CI gate) ensures these field names never appear inside a console.log() / context.log() call:

email, emailId, emailAddress, recipient, displayName, userName, ipAddress, messageContent, messageBody, messageText, sessionId, threadId, conversationId, beneficiary, purchaser, puid.

For email-related operations we log a 12-character SHA-256 hash of (recipient + subject + template) instead of the address — enough to correlate sends without re-identifying users.

Cost

App Insights uses pay-per-GB pricing. A low-volume support stack (< 1k chats/day) typically generates 50-200 MB/month of telemetry — well under the free tier of 1 GB/month/Application.