AccelerUpDocs
Administration/Datasources

Datasources

Every external system AccelerUp connects to, and what each needs.

Settings → Datasources holds every external connection. Admin only.

The list

SourceNeedsUsed by
CloudflareAPI token + account tagCloudflare
ELK / OpenSearchEndpoint, credentials, indicesLog analytics
PrometheusEndpointMetrics
JenkinsURL, user, API tokenJenkins
Jira / ConfluenceURL, user, API tokenJira, Copilot
GitHubApp or tokenCode review, changesets
Google AnalyticsService accountWeb analytics
SupersetURL, credentialsSuperset
WarehousesRead-only userConnections
Cost providersPer providerCloud spend
MySQL nodesMonitor userDatabases
ProxySQLAdmin interfaceDatabase pool
InfisicalUniversal AuthPipelines
SlackWebhook, or OAuth for sign-inChannels

Test everything

Every datasource has a Test button. Use it on creation and after every credential rotation.

Important

A datasource whose credentials expired silently looks identical to one with nothing to report. This is the single most common cause of "the monitoring stopped working and nobody noticed".

Settings → System Health shows the last successful sync per integration — check it after any credential change.

Least privilege

Every integration should use a dedicated account with the minimum access:

  • Cloudflare: read-only, only the zones you need
  • Warehouses: read-only, only the schemas you query
  • Jenkins: read, plus the specific control operations you use
  • GitHub: read, unless you use PR commenting

The account tag

Cloudflare's account tag is required for account-scoped features such as load balancers, and its absence is not obvious — zone-level pages work and account-level ones are simply empty.

Rotation

Rotating a credential: update it here, press Test, then confirm in System Health that the next sync succeeded. Do not skip the third step.

Where this behaviour lives: backend/internal/repository/postgres/integration_repo.go. If the code and this page disagree, the code is right — please fix the page.

Part of AdministrationSettings, retention, platform thresholds and change tracking.