Debug what data change triggers an analytic


#1

When an analytic is trigged, is it possible to figure out which data change (i.e., source type and source id) that triggers the analytic?


Useful TenantConfig keys
#2

Below is an answer from one of our platform engineers,

We do have a tenant config that can be used for debugging. The config id is “TimeseriesTimeRangeSourceInfoTrackingEnabled”. When enabled, this keeps track of the timeseries type, header id and source file for the change that caused the invalidation.

This tenantConfig is for debugging purpose, and not intended to be on full time.


#3

Where would one find the tracked info? (I’m assuming Splunk, but this would not be helpful to customers who don’t have access to Splunk)