@kapa.ai Where should we configure Airbyte Heartbeat. or where is this flag.yaml I have airbyte deployed in EKS via helm. Does it go under values.yaml?

The knowledge sources explain how heartbeats work and which flags control them, but they do not clearly document where

flags.yaml

lives in a Helm/EKS deployment or how to wire it via

values.yaml

. So I can’t state with certainty exactly where to place or reference

flags.yaml

in your current setup. What is documented: - Heartbeat behavior (source and destination) is controlled via

flags.yaml

with entries: -

heartbeat-max-seconds-between-messages

-

heartbeat.failSync

-

destination-timeout-max-seconds

-

destination-timeout.failSync

[[Heartbeats tech details](https://docs.airbyte.com/platform/understanding-airbyte/heartbeats#technical-details)]. - General configuration guidance for Helm installs says you should configure Airbyte by overriding the Helm chart using a

values.yaml

file, and that

values.yaml

is the main interface for configuration in Helm deployments. [[Configuring Airbyte](https://docs.airbyte.com/platform/operator-guides/configuring-airbyte); [Values.yaml reference](https://docs.airbyte.com/platform/deploying-airbyte/values); [Create values.yaml override](https://docs.airbyte.com/platform/deploying-airbyte#3-create-a-valuesyaml-override-file)] However, none of the provided docs show: - A

flags.yaml

path in the container or chart. - A

values.yaml

key that maps to

flags.yaml

content. - An example of configuring heartbeat flags via Helm. Because of that, I cannot confidently confirm that you should (or can) configure these heartbeat flags directly under

values.yaml

in your EKS Helm deployment, nor can I give you the exact keys to use. Given the current documentation: - You do configure most platform behavior via

values.yaml

overrides in Helm. [[Create values.yaml override](https://docs.airbyte.com/platform/deploying-airbyte#3-create-a-valuesyaml-override-file)] - Heartbeat settings are conceptually in

flags.yaml

, but the integration between

flags.yaml

and Helm is not described in the sources you provided. To proceed safely, you’ll likely need to: 1. Inspect the Airbyte Helm chart you’re using (e.g., the

charts/airbyte

or

charts/v2/airbyte

repo referenced in the docs) to see if there is: - A

flags.yaml

template, or - A

values.yaml

section that mentions flags/heartbeats. 2. Or, if you have access to the running pods, look for a

flags.yaml

file inside the worker/server containers to understand how it’s currently provided. But this lookup step is not documented in the knowledge sources, so I can’t give you the exact path or

values.yaml

snippet here.