​

Environments

• Tags for a small, fixed set of environments you filter by often, such as production, staging, or preview.
• Metadata when environment is part of a richer deployment context, such as environment, region, service, and deployment id.

​

Send environment as a tag

import { capture } from "@latitude-data/telemetry"

await capture(
  "support-agent-turn",
  async () => agent.run(userMessage),
  {
    tags: ["production"],
  },
)

from latitude_telemetry import capture

capture(
    "support-agent-turn",
    lambda: agent.run(user_message),
    {
        "tags": ["production"],
    },
)

​

Send environment as metadata

await capture(
  "support-agent-turn",
  async () => agent.run(userMessage),
  {
    metadata: {
      environment: "production",
      region: "us-east-1",
    },
  },
)

capture(
    "support-agent-turn",
    lambda: agent.run(user_message),
    {
        "metadata": {
            "environment": "production",
            "region": "us-east-1",
        },
    },
)

​

Use environments in Latitude

• filter traces to production traffic
• search only staging or preview traces
• save searches for production failure modes
• scope signal monitoring to a specific environment
• compare whether a behaviour appears in one environment or across all environments

​

Related

• Tags: Add lightweight environment labels
• Metadata: Attach structured deployment context
• Filters: Filter traces by tags or metadata
• Search: Search within an environment