Details
-
Sub-task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.0.0
-
None
Description
Once attributes are ingested (see SENTRY-2189), they need to be made available at runtime for use in authorization and masking actions within Sentry. For reasons of both performance and scale, these attributes will be maintained (cached) locally on the Sentry server rather then constantly pulled from the attribute ingestion source. In addition, the attributes should be highly available in situations where the connection to the attribute source might be lost and where the Sentry server might experience one or more downed nodes. Therefore, the Sentry data model will be expanded to store attribute information as a persistent backstop for the in-memory cache.