Custom Metric Data Processing in Cortex
In Cortex, it is not currently possible to manually trigger or expedite the processing of custom metric data to see results faster. This design choice is intentional and serves a specific purpose in maintaining data accuracy and consistency.
There is no supported way to force a refresh or bypass the 1-day lag for current-day data. This limitation ensures that all custom metric data points are processed and displayed uniformly across the system.
Data Lag and Display Considerations
Custom metric data points in Cortex are intentionally lagged and only displayed after the end of the previous day. This means that any data you submit for custom metrics will not be immediately visible in the user interface.
The 1-day lag is applied consistently to all custom metric data, ensuring that data from all sources is treated equally and presented in a standardized manner.
Testing and Troubleshooting
If you need to see data immediately for testing purposes, there is a workaround available. It is recommended to submit metric data with a timestamp that is at least one day in the past. This will cause the data to appear right away in the UI, allowing you to verify your custom metric setup and data submission process.
Design Rationale
The primary reason for implementing this data lag is to avoid misleading results from partial-day data. This is especially crucial for count or frequency-based metrics, where incomplete data could lead to incorrect interpretations or decisions.
By only displaying data after a full day has passed, Cortex ensures that all metrics are based on complete datasets, providing a more accurate and reliable representation of your custom metrics.