Azure Functions Telemetry

Implementation evidence

Azure Functions Telemetry: from boundary to verified row

Use Azure Functions Telemetry at a controlled application boundary, keep the event contract small, and verify a known outcome before building aggregate views.

1
Choose the outcome
Serverless function reliability
2
Define the contract
invocation_id, function_name, trigger_type, workflow, region, and release
3
Instrument the boundary
Azure Functions retry behavior varies by trigger, so record the trigger type and use the invocation context available to the handler.
4
Verify the evidence
Exercise a known fixture, then inspect azure_function_completed for one correctly typed terminal row.

Before you start

Prerequisites and boundaries

An Azure Functions app with telemetry-sh initialized outside the invocation handler
Stable function, trigger, workflow, release, and environment names
A reviewed retry policy for each trigger type and idempotent downstream work

Delivery setup

Install and initialize server-side

Import telemetry-sh in server-only code and initialize it once with process.env.TELEMETRY_API_KEY. Keep ingestion credentials out of browser bundles, client-visible environment variables, source control, logs, and exception messages.

azure-functions-install

npm installation

bash

npm install telemetry-sh

1Prepare one reusable server-side delivery client with bounded network behavior.
2Add the outcome event at the success, failure, retry, or timeout boundary.
3Send controlled fixtures and inspect the stored rows before enabling an alert.

Snippet

Start with one structured event

Add this shape where the workflow completes, fails, or retries. Then build the dashboard from real fields.

azure-functions

Azure Functions Telemetry event

javascript

await telemetry.log("azure_function_completed", {
  invocation_id: context.invocationId,
  function_name: "processBillingSync",
  trigger_type: "service_bus",
  workflow: "billing_sync",
  status: "success",
  attempt: deliveryCount,
  duration_ms: Math.round(performance.now() - startedAt),
  item_count: processedItems,
  retry_scheduled: false,
  environment: process.env.AZURE_FUNCTIONS_ENVIRONMENT,
  release: process.env.APP_RELEASE,
});

Event contract

invocation_id, function_name, trigger_type, workflow, region, and release

status, attempt, duration_ms, item_count, retry_scheduled, and error_type

message_id, route_template, account_id, dependency, and environment

Implementation checkpoints

Checkpoint 1

Azure Functions retry behavior varies by trigger, so record the trigger type and use the invocation context available to the handler.

Checkpoint 2

Emit the terminal application outcome in a finally path without turning a telemetry-delivery failure into a function failure.

Checkpoint 3

Keep trigger payloads, binding data, connection strings, authorization values, and unrestricted exception messages out of events.

Verification

Prove the event arrived

Run this after exercising known success and failure cases. Replace the fallback table name if your final event contract differs from the snippet.

azure-functions-verification

Azure Functions Telemetry verification query

sql

SELECT *
FROM azure_function_completed
ORDER BY timestamp_utc DESC
LIMIT 20;

Confirm one terminal row per logical outcome, with the expected status, identifiers, units, and UTC time.

Inspect the inferred schema and verify that retries do not change field types or generate a new logical event ID.

Search the stored fields for credentials, raw payloads, prompts, private content, and unbounded error messages.

Exercise a provider timeout, ingestion rejection, and process shutdown before treating the dashboard as complete.

Implementation references

Review the event contract, data-safety guidance, and upstream primary documentation before enabling a new production path.

Background job monitoring API reliability monitoring Retry-rate SQL Azure Functions error handling and retries Azure Functions Node.js developer guide

Production boundary

Keep the outcome event small and recoverable

This pattern provides

A bounded, SQL-ready outcome beside the upstream workflow.
Stable fields for dashboards, alerts, and cross-event correlation.
A fixture-driven path for validating success, failure, retry, and timeout behavior.

This pattern does not provide

An OTLP exporter, automatic collection pipeline, or replacement for detailed traces and diagnostic logs.
Exactly-once delivery merely because the payload contains an event ID.
Permission to collect raw provider payloads, user content, credentials, or regulated data.

Delivery and idempotency Batching and shutdown Troubleshoot ingestion

Event schema starting points

Review the row grain, emit boundary, required types, privacy classes, example payload, and validation checklist before adapting a query or snippet to production.

API reliability10 fields