Kim Gustyr

Hi @rcmosher, the fix has been released with 8.0.2. Let us know how it works for you.

Do we want to make the new properties a part of the shared [evaluation context interface](https://github.com/Flagsmith/flagsmith/blob/main/sdk/evaluation-context.json)? CC @matthewelwell @kyle-ssg

@matthewelwell We wouldn't during client runtime, but actually segmenting by app name and app version in evaluation could be desirable for the future?

I've opened a PR to update the schema here: https://github.com/Flagsmith/flagsmith/pull/5203 After it's merged, we'll be able to regenerate `evaluation-context.ts`

Same as with local identity overrides, the initial plan is to leverage the environments_v2 table to store segments. The main considerations/bottlenecks for the _local evaluation mode_ are: - DynamoDB document...

Created https://github.com/Flagsmith/flagsmith/issues/5721. Initially, I thought of serving all environment documents directly from S3 via cloudfront, but latency considerations won't allow us to do that. The epic, when implemented, will introduce...

`ghcr.io/flagsmith/flagsmith-api:pr-4400` Docker image is available for testing the backend. You can use the `/api/v1/organisations/{org_id}/integrations/grafana` analogous with the project-level one.

I propose the new keys to be named `perProject` and `perOrganisation` for consistency's sake. For backwards compatibility, consider assuming `perProject` to be true if it's not included.

@kyle-ssg The backend for this is now in staging.

Flagsmith currently offers HTTP and task processing performance metrics in Prometheus format. For a product metric use case, we can't use Prometheus labels directly as we're limited to low cardinality...