Connection Context

Connection context attaches to a specific data source whether that's a database, business application or a Count Metrics catalog. The context applies wherever that connection is used, regardless of which project references it.

Connection context can be defined via the UI in any given connection under 'Manage connection'.

or synced via the API if it needs to update automatically from your own systems:

curl -XPATCH https://api.eu.count.co/v1/connections/connection_key \
  -H"Authorization: Bearer $COUNT_API_KEY" \
  -H'Content-Type: application/json' \
  -d'{"agent_context":"This connection hosts our production warehouse..."}'

#What belongs in connection context?

Connection context might include:

• Data quirks: known issues or exceptions in the underlying data that agents need to work around, like a table that double-counts certain records before a given date.
• Definitions & naming: which field to use when a metric could be calculated more than one way, or how a column name maps to what it actually means.
• Governance & sensitivity: what shouldn't be surfaced, or needs extra care.