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>,
}Expand description
Controls Sentry-internal event processing.
Fields§
§enabled: boolTrue if the Relay should do processing. Defaults to false.
geoip_path: Option<PathBuf>GeoIp DB file source.
max_secs_in_future: u32Maximum future timestamp of ingested events.
max_session_secs_in_past: u32Maximum 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: mycustomclusterThen metrics will be produced to an entirely different Kafka cluster.
topics: TopicAssignmentsKafka topic names.
kafka_validate_topics: boolWhether 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: ByteSizeMaximum chunk size of attachments for Kafka.
projectconfig_cache_prefix: StringPrefix to use when looking up project configs in Redis. Defaults to “relayconfig”.
max_rate_limit: Option<u32>Maximum rate limit to report to clients.