What happens to custom metrics when sent more frequently?

When custom metrics are sent more frequently, the primary consequence is that more data points are consumed. Each instance of a metric being sent corresponds to data being recorded in Dynatrace, which directly impacts the amount of data stored and processed. This increase in data points can lead to higher usage metrics and might affect performance under certain conditions.

It's important to recognize that while more frequent submissions result in more detailed data collection, this can also have implications for costs associated with data handling and storage. For organizations leveraging Dynatrace for monitoring, understanding how the frequency of data points affects overall consumption and billing is crucial for managing resources effectively.

The other choices do not accurately represent the mechanics of the system in relation to custom metrics. Aggregation typically occurs when processing data for broader analytics rather than from individual submissions unless explicitly configured. Ignoring data points is not a standard behavior for Dynatrace, as the system is designed to capture all sent metrics. Lastly, there is indeed an impact on DDU (Dynatrace Data Units) consumption when the frequency of data submissions increases, so that aspect must be considered in any analysis.