Set up process #

brew install cloudquery/tap/cloudquery

1. Download CLI and login

See installation options

2. Create source and destination configs

Plugin configuration

cloudquery sync atlassian-ops-genie.yml postgresql.yml

3. Run the sync

CloudQuery sync

Overview #

The CloudQuery Opsgenie plugin pulls data out of Opsgenie and loads it into any supported CloudQuery destination (e.g. PostgreSQL, BigQuery, Snowflake, and more).

Authentication #

In order to fetch information from Opsgenie, cloudquery needs to be authenticated. An API key is required for authentication.

Opsgenie Source Plugin Configuration Reference

Example #

This example syncs from Opsgenie to a Postgres destination. The (top level) source spec section is described in the Source Spec Reference.

kind: source
# Common source-plugin configuration
spec:
  name: atlassian-ops-genie
  path: cloudquery/atlassian-ops-genie
  registry: cloudquery
  version: "v1.2.0"
  tables: ["*"]
  destinations: ["postgresql"]

  spec:
#   required fields:
    api_key: "${OPSGENIE_API_KEY}"
#   optional fields:
#    hostname: "api.eu.opsgenie.com"

Opsgenie Spec #

This is the (nested) spec used by the Opsgenie source plugin.

api_key (string) (required)
An API key to access the Opsgenie API.
hostname (string) (optional) (default: api.opsgenie.com)
Hostname of the Opsgenie API. If using the EU instance of Opsgenie, the URL needs to be api.eu.opsgenie.com. See https://docs.opsgenie.com/docs/api-overview.
concurrency (integer) (optional) (default: 10)
A best effort maximum number of Go routines to use. Lower this number to reduce memory usage.
scheduler (string) (optional) (default: dfs) The scheduler to use when determining the priority of resources to sync. Supported values are dfs (depth-first search), round-robin, shuffle and shuffle-queue.
For more information about this, see performance tuning.