Expand description
Event normalization and processing.
Modules§
- Computation of breakdowns from event data.
- Computation and normalization of contexts from event data.
- Contains helper function for NEL reports.
- Validation and normalization of
Replay
events. - Normalization of the
Request
interface. - Span normalization logic.
- Generate context data from user agent and client hints.
- Deprecated. Utilities for extracting common event fields.
Structs§
- Borrowed version of
SpanOpDefaults
. - Configuration for computing breakdowns from data in the event.
- Defines a builtin measurement.
- The client hint variable names mirror the name of the “SEC-CH” headers.
- Corrects clock drift based on the sender’s and receivers timestamps.
- Container for global and project level
MeasurementsConfig
. The purpose is to handle the merging logic. - Configuration for
validate_event
. - A geo ip lookup helper based on maxmind db files.
- Configuration for measurements normalization.
- A single mapping of (AI model ID, input/output, cost)
- A mapping of AI model types (like GPT-4) to their respective costs.
- Configuration for
normalize_event
. - Defines the performance configuration for the project.
- Defines a profile for performance score.
- Defines a weighted component for a performance score.
- A container housing both the user-agent string and the client hint headers.
- Removes unknown, internal and deprecated fields from a payload.
- Validates constraints such as empty strings or arrays and invalid characters.
- The rule describes how span descriptions should be changed.
- Object containing transaction attributes the rules must only be applied to.
- A rule to infer
Span::op
from other span fields. - Rules used to infer
span.op
from other span fields. - Configuration to define breakdowns based on span operation name.
- A time window declared by its start and end timestamp.
- Ensures an event’s timestamps are not stale.
- Configuration for sanitizing unparameterized transaction names.
- The rule describes how transaction name should be changed.
- Rejects transactions based on required fields.
- Limits properties to a maximum size and depth.
Enums§
- Configuration to define breakdown to be generated based on properties and breakdown type.
- Describes what to do with the matched pattern.
Traits§
- Computes a
Context
from either a user agent string and client hints.
Functions§
- Applies the rule if any found to the transaction name.
- The sec-ch-ua field looks something like this: “Not_A Brand”;v=“99”, “Google Chrome”;v=“109”, “Chromium”;v=“109” The order of the items are randomly shuffled.
- Returns
true
if the event’s transaction name is known to contain unsanitized values. - Returns
true
if the given platform string is a known platform identifier. - Replaces snake_case app start spans op with dot.case op.
- Computes breakdowns for an event based on the given configuration.
- Normalizes an event.
- Ensure only valid measurements are ingested.
- Computes performance score measurements for an event.
- Apply parametrization to transaction.
- Generates context data from client hints or user agent.
- Low-level version of
normalize_user_agent
operating on parts. - Set a default transaction source if it is missing, but only if the transaction name was extracted as a metrics tag. This behavior makes it possible to identify transactions for which the transaction name was not extracted as a tag on the corresponding metrics, because source == null <=> transaction name == null See
relay_server::metrics_extraction::transactions::get_transaction_name
. - Given a string checks if the environment name is generally valid.
- Validates an event.
- Given a string checks if the release is generally valid.
- Validates a span.
Type Aliases§
- An error in the
GeoIpLookup
.