Date of slack thread: 5/29/24
Anonymous: Hi Statbot, Some time ago we disabled precomputed metric ingestion to refactor how they are being computed on our side and would now like to reenable them again. I have setup a new connection, edited the SQL query and setup the column mapping. Running the query from within the Statsig interface gives back the results, so it seems like everything is setup correctly. But it doesn’t seem like the ingestion job is running for us (both daily and requested backfills) and at the same time I can’t find any errors or notifications that something is not configured correctly.
Anonymous: I don’t actually see the ingestion statuses of “succeeded, succeeded with no data detected, and failed” which leads me to believe that the ingestion is not getting scheduled for our case(?)
Timothy Chan (Statsig): Hi Deniss, I believe I know what’s going on. Let me tag someone who can help. <@U05TAM7MRAQ>
Chong Xie (Statsig): Our system is having trouble establishing a connection with your warehouse. We’re still looking into it, apologies for the delay.
AJ Liu (Statsig): Hi <@U071XN56K2B>! I’m looking into the issue and would like to confirm something with you. Have you allowlist all the IPs here in your firewall setting? https://docs.statsig.com/infrastructure/statsig_ip_ranges#outbound-statsig---your-servers The actual data import setup has different setup than the console query, so you need to allowlist all the IP ranges provided in the doc.