If you’re already reporting events to Google Cloud Platform (GCP) Pub/Sub you can leverage Stigg’s native connector to forward these events to Stigg and track feature usage.
Under the hood, the connector leverages a GCP Function designed to actively listen to a Pub/Sub topic, map events to the Stigg event schema format and send them to Stigg in batches at one-second intervals.
terraform/terraform.tfvars
file with the following content and fill in the values:
cd terraform/
terraform init
to initialize the projectterraform apply -var-file=".tfvars"
to deploy the Cloud FunctionTo allow Stigg to meter feature usage based on reported events, an event-based metered feature must exist in Stigg.
If you haven’t defined a meter for these events in Stigg yet, click here to learn how to do so.
Example integration of GCP Pub/Sub with Stigg for usage metering.
If you’re already reporting events to Google Cloud Platform (GCP) Pub/Sub you can leverage Stigg’s native connector to forward these events to Stigg and track feature usage.
Under the hood, the connector leverages a GCP Function designed to actively listen to a Pub/Sub topic, map events to the Stigg event schema format and send them to Stigg in batches at one-second intervals.
terraform/terraform.tfvars
file with the following content and fill in the values:
cd terraform/
terraform init
to initialize the projectterraform apply -var-file=".tfvars"
to deploy the Cloud FunctionTo allow Stigg to meter feature usage based on reported events, an event-based metered feature must exist in Stigg.
If you haven’t defined a meter for these events in Stigg yet, click here to learn how to do so.
Example integration of GCP Pub/Sub with Stigg for usage metering.