Skip to main content
Project Owner or Editor privileges in Google Cloud are required to complete this setup.

​
Create or select a Google Cloud project

To use the Cloud Logging and Cloud Monitoring APIs with OAuth 2.0, you need a Google Cloud project.

1

Sign in to Google Cloud

Sign in to your Google Cloud Console.

Google sign-in page for Google Cloud Platform with the Email or phone field and the Next button highlighted.
2

Create or select a project

Select an existing project from the dropdown at the top of the page, or create a new one by clicking New Project and filling in the Project name, Organization, and Parent resource fields, then clicking Create.

Select a resource dialog listing the projects in the organization, with the New project button highlighted.

​
Enable the Cloud Logging API and Cloud Monitoring API

Navigate to APIs & Services > Library, search for each API below, click on it, then click Enable. If it already shows Manage, the API is already enabled.

  • Cloud Logging API
  • Cloud Monitoring API
Product details page for the Cloud Logging API in the API Library, showing the API Enabled status with the Enable/Manage button highlighted.

​
Configure Google Auth Platform

Before creating OAuth credentials, ensure Google Auth Platform is configured.

1

Navigate to Google Auth Platform

In the Google Cloud Console, go to APIs & Services > OAuth consent screen. This will open the Google Auth Platform dashboard.

2

Start configuration

If you have already configured Auth Platform (the OAuth Overview page with usage metrics is shown), skip this step and navigate to the Branding page from the sidebar. Otherwise, you will see a Get started button — click it to begin the configuration process.

3

Enter app information

Fill in the required fields for your application.

  • App name: Enter a name for your application (e.g., StackOne GCP Observability Integration).
  • User support email: Select an email for user inquiries.
  • Click Next to continue.
  • Note: If you already have an existing OAuth consent screen configuration, you can edit the details in this and the following steps.
Branding page of the Google Auth Platform with the App information section, highlighting the App name and User support email fields (email redacted).
4

Select audience

Choose the appropriate user type for your application.

  • Internal: Only users within your Google Workspace organization can authorize (no app verification required).
  • External: Any Google account can authorize (requires app verification for production use).
  • Click Next to continue.
Audience page of the Google Auth Platform with the User type section highlighted, showing the current type and the Make internal button.
5

Enter contact information

Provide email addresses for Google to notify you about any changes to your project. Click Next to continue.

6

Finish configuration

Review your settings, agree to the Google API Services User Data Policy, and click Create to complete the setup.

​
Configure scopes

In Google Auth Platform, go to Data Access and click Add or Remove Scopes to configure the OAuth scopes your application needs.

Data Access page of the Google Auth Platform with the Add or remove scopes button highlighted above the list of configured scopes.
1

Add scopes

Enables actions: Create Alert Policy, Create Dashboard, Create Exclusion, Create Log Metric, Create Notification Channel, Create Sink, Create Uptime Check Config, Delete Alert Policy, Delete Dashboard, Delete Exclusion, Delete Log, Delete Log Metric, Delete Notification Channel, Delete Sink, Delete Uptime Check Config, Get Alert Policy, Get Dashboard, Get Exclusion, Get Log Metric, Get Metric Descriptor, Get Notification Channel, Get Sink, Get Uptime Check Config, List Alert Policies, List Dashboards, List Exclusions, List Log Entries, List Log Metrics, List Logs, List Metric Descriptors, List Monitored Resource Descriptors, List Notification Channels, List Sinks, List Time Series, List Uptime Check Configs, Test Auth, Update Alert Policy, Update Dashboard, Update Exclusion, Update Log Metric, Update Notification Channel, Update Sink, Update Uptime Check Config, Verify Notification Channel, Write Log Entries

Add the required Google Cloud Logging and Monitoring scopes for your integration.

2

Select scopes from the list

In the Update selected scopes side panel that opens, check the required scopes from the list.

Update selected scopes side panel with the scope table highlighted, showing the logging and monitoring scopes checked.
3

Manually add scopes (if needed)

If a required scope is not shown in the list, use the Manually add scopes section.

  • Enter the full scope URL in the input field.
  • Click Add to table.
4

Apply and save

Confirm and persist your scope configuration.

  • Click Update to apply the selected scopes. The side panel will close.
  • On the Data Access page, click Save to persist the scope configuration.

​
Create OAuth 2.0 client credentials

Set up OAuth client credentials to authenticate with Cloud Logging and Cloud Monitoring APIs. If you already have an existing OAuth 2.0 client, you can reuse it by adding the StackOne redirect URI and generating a new secret.

Credentials page under APIs & Services with the + Create credentials button highlighted.
1

Navigate to Credentials

In the Google Cloud Console, go to APIs & Services > Credentials.

Create credentials menu open on the Credentials page with the OAuth client ID option highlighted.
2

Option A — Create a new OAuth client

Skip this step if you are using an existing client.

  • Click + Create Credentials and select OAuth client ID.
  • Select Web application as the application type.
  • Enter a Name for your OAuth client (e.g., StackOne Cloud Observability Integration).
  • Under Authorized redirect URIs, click Add URI and enter https://api.stackone.com/connect/oauth2/googlecloudobservability/callback.
  • Click Create. A dialog will display your Client ID and Client Secret — copy and store them securely.
Create OAuth client ID form with Application type set to Web application, a Name filled in, the StackOne callback URL under Authorized redirect URIs, and the Create button highlighted.
3

Option B — Use an existing OAuth client

Skip this step if you created a new client above.

  • Click on your existing OAuth 2.0 client ID from the list.
  • Under Authorized redirect URIs, click Add URI, enter https://api.stackone.com/connect/oauth2/googlecloudobservability/callback, and click Save.
  • Under Client secrets, click + Add secret to generate a new secret. Copy it and store it securely — it will not be shown again.
  • Your Client ID is shown on the same page under Additional information.
Existing OAuth client page highlighting the Authorized redirect URIs field, the Save button, the Client ID under Additional information (redacted) and the Add secret button under Client secrets.

​
Creating the StackOne Connector Profile

To create the Connector Profile in StackOne for Google Cloud Observability:
1

Navigate to Connector Profiles

Login to StackOne and navigate to Connector Profiles
2

Create New Connector Profile

  • Click + Connector Profile
  • Search for and select Google Cloud Observability
  • Select Type as OAuth 2.0
  • Fill out the fields using details retrieved from your provider:
    • Client ID
    • Client Secret
    • Scopes (Optional)
  • (Optional) Select Actions to be enabled for this Connector Profile
  • Click Create profile
Congratulations! The new Connector Profile will now show up in your project ready to be used. You can now continue to Link Accounts for Google Cloud Observability.