Cloud Profiler API

Name: Cloud Profiler API API
Brand: Cloud Profiler API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsMonitoring Observabilityoauth24 EndpointsREST

For Agents

Submit and patch CPU and heap profiles from applications running on or off Google Cloud. Used by profiling agents and offline tooling that feed Cloud Profiler's flame graphs and comparison views.

Quickstart

Get started with Cloud Profiler API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"submit a profile to google cloud profiler"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Cloud Profiler API API.

Submit profile data captured by an in-process profiling agent

Submit offline profile data captured outside Google Cloud

Patch an active profile with sampled data and metadata

Use Cases

GET STARTED

Start building with Cloud Profiler API API

Explore with Jentic

View OpenAPI Document

Use for: I need to start a CPU profiling session for my service, Submit a heap profile sample collected by my agent, Send an offline profile captured from a non-GCP host, Check whether the profiler accepted my last upload

Not supported: Does not capture metrics, run distributed traces, or store logs — use for CPU and heap profile submission to Cloud Profiler only.

Google Cloud Profiler is a managed continuous-profiling service that gathers CPU and heap profiles from production applications with negligible overhead. The API is small and primarily agent-facing: profiling agents embedded in applications call createProfile to register a profiling session, then upload sampled profile data via patch operations. Offline reporting tools use createOfflineProfile to submit profile data captured outside Google Cloud, allowing the same flame-graph and comparison tooling to surface non-GCP workloads.

★ Continuous Production CPU Profiling

Engineering teams embed the Cloud Profiler agent in production binaries; the agent calls createProfile to claim a profiling slot for the deployment, samples the running process for the configured profile type, and patches the resulting profile back to Cloud Profiler. The flame graph in the console then shows where CPU time goes across versions and zones.

Call POST /v2/{parent}/profiles with a deployment payload, then PATCH /v2/{name} with the captured profile bytes

Offline Profile Submission for Non-GCP Workloads

Teams running workloads outside Google Cloud capture profiles with their own tooling and call createOfflineProfile to submit them. The same flame-graph view and comparison tooling that supports GCP workloads is then available for on-prem or other-cloud services, giving a single profiling surface across heterogeneous deployments.

Call POST /v2/{parent}/profiles:createOffline with a populated profile message including deployment, profileType, and the captured profileBytes

AI Agent Performance Analyst via Jentic

An agent invoked during a performance investigation searches Jentic for the right Cloud Profiler operation, submits a captured profile, and points a human at the resulting flame graph. For ad-hoc analysis on non-GCP hosts, the agent uses createOfflineProfile so the same console view applies.

Search Jentic for 'submit offline profile to google cloud', execute against POST /v2/{parent}/profiles:createOffline with the captured bytes, and report the resulting profile name

Key Endpoints

4 endpoints — google cloud profiler is a managed continuous-profiling service that gathers cpu and heap profiles from production applications with negligible overhead.

METHOD

PATH

DESCRIPTION

POST

/v2/{+parent}/profiles

Create a new profiling session for a deployment

POST

/v2/{+parent}/profiles:createOffline

Submit an offline profile captured outside Google Cloud

PATCH

/v2/{+name}

Patch a profile with captured sample bytes

POST

/v2/{+parent}/profiles

Create a new profiling session for a deployment

POST

/v2/{+parent}/profiles:createOffline

Submit an offline profile captured outside Google Cloud

PATCH

/v2/{+name}

Patch a profile with captured sample bytes

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Google Cloud OAuth 2.0 credentials and service account keys are stored encrypted in the Jentic vault. Agents receive short-lived access tokens scoped to cloud-platform — raw service account JSON never enters the agent context.

Intent-based discovery

Agents search Jentic by intent (e.g. 'submit profile to google cloud profiler') and Jentic returns the matching operation with its parameter schema, so the agent can call the right endpoint without reading Discovery docs.

Time to first call

Direct Cloud Profiler integration: half a day for OAuth and profile-format setup if not using a built-in language agent. Through Jentic: under an hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Cloud Monitoring API

Captures metrics that pair with profiler flame graphs for full performance investigation

Use Cloud Monitoring for time-series metrics; use Cloud Profiler when you need stack-level attribution of CPU or heap usage

Complementary

Cloud Logging API

Holds the application logs that contextualise a slow profile sample

Use Cloud Profiler to find a hotspot; use Cloud Logging to read the surrounding logs that explain why

Complementary

Error Reporting API

Surfaces grouped exceptions that may correlate with profile hotspots

Use Cloud Profiler for performance hotspots; use Error Reporting when the underlying issue is a thrown exception rather than slow code

FAQs

Specific to using Cloud Profiler API API through Jentic.

What authentication does the Cloud Profiler API use?

The Cloud Profiler API uses OAuth 2.0 with the cloud-platform or monitoring.write scope. Tokens are issued for a Google service account or end user. Through Jentic, the OAuth credential lives in the Jentic vault and the agent receives a short-lived access token only — the underlying service account JSON never enters agent context.

Can I submit profiles from a service running outside Google Cloud?

Yes. Use POST /v2/{parent}/profiles:createOffline with a profile message that includes deployment metadata (target, labels), profileType (CPU, HEAP, WALL, etc.), and the captured profileBytes. The same console view that supports on-GCP profiling shows the resulting flame graphs.

What are the rate limits for the Cloud Profiler API?

Cloud Profiler ingestion quotas are published in the Google Cloud console under the Cloud Profiler API quota page; the API is designed for low-frequency uploads from continuous agents (typically one profile per minute per process), so per-project quotas are sized accordingly.

How do I start a profiling session through Jentic?

Search Jentic for 'create google cloud profile' and execute the returned operation against POST /v2/{parent}/profiles with a Deployment payload that names the service, version, and zone. The response includes a profile name and the agent then patches it with sampled data.

Which profile types does Cloud Profiler support?

Cloud Profiler supports CPU, WALL, HEAP, HEAP_ALLOC, CONTENTION, and THREADS profile types depending on the language runtime. The supported set is included in the createProfile request and the agent samples accordingly. Offline uploads can carry any of the supported types.

Is Cloud Profiler free?

Cloud Profiler is included with Google Cloud at no separate cost; only the runtime resources consumed by the profiling agent are billed under the host service. Pricing is documented on the Cloud Profiler pricing page.