feature-request

Expand external log drain with environment identifier

Please add environment_identifier to exported logs so we can have a name instead of hash for switching between environment log views in our Grafana log dashboard.

Reference documentation here.

Proposed fields:

  • If NDJSON - Headers is selected, X-Cycle-Environment-Identifier header is added.
  • If NDJSON - Raw is selected, environment_identifier field is added.

The value is the same as identifier field in environment settings page.

Example NDJSON raw request body:

{
  "time": "2025-08-07T11:11:11.12345678Z",
  "source": "stdout",
  "message": "some log message",
  "instance_id": "instanceid",
  "environment_id": "environmentid",
  "environment_identifier": "my-environment",    <---- please add this
  "container_id": "containerid",
  "container_identifier": "my-container",
  "container_deployment": "my-deployment",
  "server_id": "serverid"
}

*the json in example above was formatted for convenience. NDJSON body actually contains one json object per line, each representing a log message.

avatar
2
  • Love the detail in these requests, thank you so much for that.

    I'll bring this up also at the next eng meeting or find out if theres another, simpler way to get that info into your grafana.

    You're mostly just looking to have a string value for the environment thats not some random ID/hash for ease of parsing on the grafana side right?

    avatar
    platform
  • You're mostly just looking to have a string value for the environment thats not some random ID/hash for ease of parsing on the grafana side right?

    Yes, exactly.

    avatar
v2025.08.04.01 © 2024 Petrichor Holdings, Inc.

We use cookies to enhance your experience. You can manage your preferences below.