Modal logo
IntroductionCustom container images Custom containersPrivate registriesGPUs and other resources GPU accelerationUsing CUDA on ModalReserving CPU and memoryScaling out Scaling outDicts and queuesJob processingConcurrent inputs on a single container (beta)Dynamic batching (beta)Secrets and environment variables SecretsEnvironment variablesDeployment Apps, Stubs, and entrypointsManaging deploymentsInvoke deployed functionsContinuous deploymentScheduling and cron jobsWeb endpoints Web endpointsStreaming endpointsWeb endpoint URLsRequest timeoutsTunnels (beta)Data sharing and storage Passing local dataVolumesMounting local files and directoriesStoring model weightsDataset ingestionCloud bucket mounts (Beta)Network file systems (superseded)Dynamic sandboxesPerformance Cold start performanceMemory Snapshot (beta)Geographic latencyReliability and robustness Failures and retriesPreemptionTimeoutsTroubleshootingSecurity and privacyIntegrations Connecting Modal to your Vercel accountConnecting Modal to your Datadog accountConnecting Modal to your OpenTelemetry providerOkta SSOOther topics File and project structureDeveloping and debuggingModal user account setupWorkspacesEnvironmentsJupyter notebooksAsynchronous API usageGlobal variablesRegion selectionContainer lifecycle hooksParameterized functionsS3 Gateway endpoints

Connecting Modal to your OpenTelemetry Provider

You can export Modal logs to your OpenTelemetry provider using the Modal OpenTelemetry integration. This integration is compatible with any observability provider that supports the OpenTelemetry HTTP APIs.

What this integration does

This integration allows you to:

  1. Export Modal audit logs to your provider
  2. Export Modal function logs to your provider
  3. [Coming Soon] Export container metrics to your provider

Installing the integration

  1. Find out the endpoint URL for your OpenTelemetry provider. This is the URL that the Modal integration will send logs to. Note that this should be the base URL of the OpenTelemetry provider, and not a specific endpoint. For example, for the US New Relic instance, the endpoint URL is https://otlp.nr-data.net, not https://otlp.nr-data.net/v1/logs.
  2. Find out the API key or other authentication method required to send logs to your OpenTelemetry provider. This is the key that the Modal integration will use to authenticate with your provider. Modal can provide any key/value HTTP header pairs. For example, for New Relic, the header is api-key.
  3. Create a new OpenTelemetry Secret in Modal with one key per header. These keys should be prefixed with OTEL_HEADER_, followed by the name of the header. The value of this key should be the value of the header. For example, for New Relic, an example Secret might look like OTEL_HEADER_api-key: YOUR_API_KEY. If you use the OpenTelemetry Secret template, this will be pre-filled for you.
  4. Navigate to the Modal metrics settings page and configure the OpenTelemetry push URL from step 1 and the Secret from step 3.
  5. Save your changes and use the test button to confirm that logs are being sent to your provider. If it’s all working, you should see a Hello from Modal! 🚀 log from the modal.test_logs service.

Uninstalling the integration

Once the integration is uninstalled, all logs will stop being sent to your provider.

  1. Navigate to the Modal metrics settings page and disable the OpenTelemetry integration.