Concepts

Automatic syncing

Turn off the schedule Costfluent collects your cloud cost data on, and read what stops and what keeps working.

Costfluent collects cost data from your connected data sources on its own schedule, by default once a day. Every one of those collections reads from your cloud account, and some of those reads are metered by the provider and billed to you, such as Cost Explorer queries on AWS.

Automatic syncing is the switch over that schedule. It is on for every workspace until somebody turns it off.

Before you start

Open Settings, then Workspaces, select the workspace, and use the Automatic syncing card. The change applies to that workspace only.

The Automatic syncing card with its switch on and the note that a data source another workspace also uses keeps syncing for that workspace — The Automatic syncing card of a workspace that syncs on the schedule.

What stops

The scheduled collection, and the credential check that runs beside it. Costfluent stops calling the data sources this workspace uses on its own initiative, so the calls stop appearing in your provider's API metering.

What keeps working

Every cost record already collected. Nothing is deleted, hidden or re-scoped.
Cost reports, dashboards, budgets, alerts and the Public API, over the data that was collected before syncing was turned off.
Sync on a connection. A collection somebody asks for explicitly still runs, which is how you bring a paused workspace up to date without turning the schedule back on.

New cost data stops arriving until you turn automatic syncing back on, so figures for the days in between fill in on the next collection rather than appearing as zero.

Sync a connection by hand

Open Settings, then Integrations, and select the provider.
On the connection's row, select the Sync button. The page confirms "Sync started".

The button appears for people allowed to sync connections, and not for upload-based integrations. It is disabled while a sync runs. "Sync not started" means Costfluent refused the request, for example because a sync is already running or one ran a moment ago.

Data sources shared with another workspace

A data source is connected once for the organization and then enabled in the workspaces that use it. Costfluent keeps a source on its schedule while at least one workspace has it enabled and syncs automatically, so a source another workspace still syncs keeps updating, for that workspace and for yours, since the cost data is the same data. The card says so: "A data source another workspace also uses keeps syncing for that workspace."

A data source that is linked to no workspace at all keeps syncing, because no workspace has said anything about it. A source linked to workspaces but switched off in every one of them stops.

A data source stays on the schedule while a workspace that has it enabled syncs automatically, or while it is linked to no workspace at all; a source switched off in every workspace it is linked to stops.

Public API

The setting is part of the workspace object. See Authentication for tokens, and the API Reference for the full schemas.

Read whether a workspace syncs automatically:

Code
curl -H "Authorization: Bearer $COSTFLUENT_API_TOKEN" \
  https://api.costfluent.com/v1/workspaces/wsp_example

Turn automatic syncing off:

Code
curl -X PUT \
  -H "Authorization: Bearer $COSTFLUENT_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"enableAutomaticSyncing": false}' \
  https://api.costfluent.com/v1/workspaces/wsp_example

Collect on demand while it is off. The response's triggered is false when Costfluent refused the request:

Code
curl -X POST \
  -H "Authorization: Bearer $COSTFLUENT_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"fullSync": false}' \
  https://api.costfluent.com/v1/providers/prv_example/sync

"fullSync": true collects your plan's whole backfill instead of the next window: the older months the connection's first collection did not reach, as far back as the provider still holds data, and the months it already holds again. It is what Collect older months sends (Manage connections). It counts toward this month's usage, and Costfluent accepts one for a connection every 24 hours; inside that wait, triggered is false and message says when to try again.

Currency settings Connect AWS