Environments

In Mydle, “environment” appears in two related forms:

• Telemetry tag — a string field on log entries, traces / spans, browser events, and some monitor job metadata (for example production, staging).
• Deployment environment — a named catalog row (deployment_environments) with kind production, staging, development, preview, or custom, used by Deployment Intelligence.

Reliability work mixes prod and non-prod constantly. Tagging environments lets explorers and impact views restrict to what you actually care about without inventing topology. Correlation still prefers explicit IDs (trace_id, session_id) over environment alone.

1. Logs — set environment on createMydleLogger or per event. If omitted, the source default_environment applies.
2. Traces — OTLP resource / span attributes map to stored environment; sources also carry default_environment.
3. Browser — SDK beacons carry project / release context; environment defaults are stored with browser records (product default production when applicable).
4. Search — log queries accept field filters such as environment:production (and alias env:).

import { createMydleLogger } from "@mydle/logs";

const logger = createMydleLogger({
  apiKey: "sk_live_YOUR_SECRET_KEY",
  service: "checkout",
  environment: "staging",
});

logger.warn("payment gateway slow", {
  environment: "staging",
  labels: { region: "eu" },
});

When Deployment Intelligence is entitled (Pro+), workspaces can maintain deployment environment catalog entries and attach releases / deployment events to them. List via authenticated API GET /environments (Enterprise API access) or the product UI when the surface is enabled.

Deployment records are observed CI/CD events only — Mydle does not invent deploy history.

• Log / trace source default_environment in the product when creating a source
• SDK options: environment on @mydle/logs; release on @mydle/browser-sdk
• OpenTelemetry resource attributes for deployment environment on OTLP ingest — see OpenTelemetry

• Environment is a filter dimension, not a separate billable product line.
• Deployment Intelligence requires Pro+ (deployment_intelligence).
• Exact max count of deployment environment rows per workspace: Not currently published.
• Allowed custom environment string length / charset: Not currently published.

• Concepts
• Log search & filtering
• Tracing
• Projects & Workspaces
• Limits & Quotas