ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
NetBox persists timestamps in PostgreSQL as UTC and renders them in the web UI according to each user's preferred time zone, defaulting to the installation-wide TIME_ZONE setting when no preference is set. The REST API serializes datetime fields as ISO 8601 strings in UTC, leaving regional interpretation to the client. The dcim.Site model includes an optiona
Goal: Enable distributed services that publish to NATS JetStream to receive message timestamps in a shared timezone without each subscriber performing its own conversion. Constraint: NATS Core treats payloads as opaque and JetStream stores timestamps as UTC nanoseconds, leaving timezone handling to applications; there is no built‑in mechanism to adjust or no
Goal: store a timestamp attribute that supports correct chronological ordering for range queries and enables prefix‑based filters when used as a DynamoDB sort key. Constraint: the attribute must be stored in a single canonical format because mixing UTC ISO 8601 strings, offset‑containing strings, or epoch numbers breaks lexicographic or numeric sort order an
Goal: Ensure that a Datadog query can combine timestamps expressed as epoch milliseconds (without an explicit zone) and ISO‑8601 strings that include a UTC offset without triggering a validation failure. Constraints: Datadog’s query editor rejects any request where some timestamps lack a timezone offset, returning the error “all time values must include a ti
Determine whether the JetStream Timestamp field records the instant the leader replica accepts a message or the moment the message is durably written to storage. The NATS server generates the Timestamp using time.Now().UTC() at acceptance and offers no configuration to shift or delay it. Under heavy load or during network partitions, the durability lag can c
nats
dynamodb
datadog