Struct Processing 

pub struct Processing {

    pub enabled: bool,
    pub geoip_path: Option<PathBuf>,
    pub max_secs_in_future: u32,
    pub max_session_secs_in_past: u32,
    pub kafka_config: Vec<KafkaConfigParam>,
    pub secondary_kafka_configs: BTreeMap<String, Vec<KafkaConfigParam>>,
    pub topics: TopicAssignments,
    pub kafka_validate_topics: bool,
    pub redis: Option<RedisConfigs>,
    pub attachment_chunk_size: ByteSize,
    pub projectconfig_cache_prefix: String,
    pub max_rate_limit: Option<u32>,
    pub quota_cache_ratio: Option<f32>,
    pub quota_cache_max: Option<f32>,
    pub upload: UploadServiceConfig,
}

Controls Sentry-internal event processing.

Fields

enabled: bool

True if the Relay should do processing. Defaults to false.

geoip_path: Option<PathBuf>

GeoIp DB file source.

max_secs_in_future: u32

Maximum future timestamp of ingested events.

max_session_secs_in_past: u32

Maximum age of ingested sessions. Older sessions will be dropped.

kafka_config: Vec<KafkaConfigParam>

Kafka producer configurations.

secondary_kafka_configs: BTreeMap<String, Vec<KafkaConfigParam>>

Additional kafka producer configurations.

The kafka_config is the default producer configuration used for all topics. A secondary kafka config can be referenced in topics: like this:

secondary_kafka_configs:
  mycustomcluster:
    - name: 'bootstrap.servers'
      value: 'sentry_kafka_metrics:9093'

topics:
  transactions: ingest-transactions
  metrics:
    name: ingest-metrics
    config: mycustomcluster

Then metrics will be produced to an entirely different Kafka cluster.

topics: TopicAssignments

Kafka topic names.

kafka_validate_topics: bool

Whether to validate the supplied topics by calling Kafka’s metadata endpoints.

redis: Option<RedisConfigs>

Redis hosts to connect to for storing state for rate limits.

attachment_chunk_size: ByteSize

Maximum chunk size of attachments for Kafka.

projectconfig_cache_prefix: String

Prefix to use when looking up project configs in Redis. Defaults to “relayconfig”.

max_rate_limit: Option<u32>

Maximum rate limit to report to clients.

quota_cache_ratio: Option<f32>

Configures the quota cache ratio between 0.0 and 1.0.

The quota cache, caches the specified ratio of remaining quota in memory to reduce the amount of synchronizations required with Redis.

The ratio is applied to the (per second) rate of the quota, not the total limit. For example a quota with limit 100 with a 10 second window is treated equally to a quota of 10 with a 1 second window.

By default quota caching is disabled.

quota_cache_max: Option<f32>

Relative amount of the total quota limit to which quota caching is applied.

If exceeded, the rate limiter will no longer cache the quota and sync with Redis on every call instead. Lowering this value reduces the probability of incorrectly over-accepting.

Must be between 0.0 and 1.0, by default there is no limit configured.

upload: UploadServiceConfig

Configuration for attachment uploads.

Trait Implementations

impl Debug for Processing

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for Processing

fn default() -> Self

Constructs a disabled processing configuration.

impl<'de> Deserialize<'de> for Processing

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl Serialize for Processing

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.