Use Platform Tools
Access the Granica API explorer, Grafana dashboards, Airflow DAG scheduler, and Spark History Server directly from the Granica Console.
The Platform Tools section of the sidebar provides direct, authenticated access to four backend services embedded within the Granica Console. All four tools are proxied through the Console's authentication layer — you do not need separate credentials to access them.
| Tool | Access | Roles |
|---|---|---|
| Granica API | /granica-api/docs | Admin only |
| Grafana | /grafana/ | Admin, Editor |
| Airflow | /airflow/ | Admin only |
| Spark History | /sparkhistory/ | Admin, Editor |
Granica API
Access level: Admin only
The Granica API tool opens the interactive Swagger/ReDoc documentation for the Granica REST API, served directly from the backend. From this interface, Admins can browse every available endpoint, inspect request and response schemas, and execute API calls live against your Granica deployment.
Exercise extreme caution. The Granica API gives direct access to every operation the platform can perform — including creating, modifying, and deleting tables, triggering crunch and vacuum jobs, and changing policies. Mutating operations (POST, PUT, PATCH, DELETE) execute immediately against your live data. There is no undo. Use this tool only when you need low-level access that the Console UI does not expose, and prefer read-only GET requests for exploration.
Access control:
GETrequests (read) — available to all authenticated usersPOST,PUT,PATCH,DELETErequests (write) — Editors and Admins only/docs,/redoc,/openapi.json(API documentation UI) — Admins only
API keys with explicit scopes are also enforced here — a key with only tables:read cannot trigger a crunch job even through the direct API. See API Keys for scope definitions.
For the full API reference, see Granica APIs V1.
Grafana
Access level: Admin, Editor
Grafana provides deep operational dashboards for the Granica platform infrastructure — cluster health, job throughput, resource utilization, error rates, and latency metrics collected from Granica's internal telemetry.
Grafana is a read-only observability tool. It surfaces metrics from the Granica data plane running in your cloud environment and is the recommended tool for:
- Investigating performance anomalies or slow crunch jobs
- Monitoring cluster resource utilization (CPU, memory, disk I/O)
- Tracking job queue depth and worker availability
- Setting up alert rules for infrastructure health
Your Granica Console role maps directly to a Grafana org role: Admins get Grafana Admin access, Editors get Grafana Editor access, and Viewers (who cannot access Grafana through the Console) would get Viewer access if granted. No separate Grafana login is required.
Airflow
Access level: Admin only
Apache Airflow is Granica's workflow scheduler. It orchestrates the DAGs (Directed Acyclic Graphs) that drive background crunch jobs, metadata collection, catalog syncs, and other scheduled platform operations.
Exercise extreme caution. Airflow gives direct control over the pipelines that process and write your data. Manually triggering, pausing, or clearing DAG runs can cause duplicate processing, missed optimizations, or unintended writes to your datasets. Only interact with Airflow if you have been specifically instructed to do so by Granica support, or if you fully understand the consequences of the operation.
Common legitimate use cases for accessing Airflow:
- Checking the status of a stuck or delayed DAG run during troubleshooting
- Reviewing task logs to diagnose a pipeline failure (read-only)
- Coordinating with Granica support on a specific DAG
Your Console Admin role maps to Airflow's Admin FAB role, which grants full access to all DAGs and operations. Avoid triggering, re-running, or clearing tasks unless directed.
Spark History
Access level: Admin, Editor
The Spark History Server (SHS) provides a detailed execution log for every Spark job that Granica has run — including all crunch, optimize, and vacuum jobs. It is the primary tool for diagnosing individual job performance and failures at the Spark level.
The Spark History Server is read-only — it provides historical execution data and cannot trigger any new operations. It is safe to explore freely.
Use the Spark History Server to:
- Inspect the execution plan and stage breakdown for a specific crunch job
- Identify data skew, spill, or shuffle bottlenecks in a slow job
- View detailed task-level timing and I/O metrics
- Cross-reference a job with the Activities dashboard using the Spark App ID
From the Activities dashboard, clicking on a Crunch Jobs row opens the Spark History Server detail panel for that job directly within the Console, so you rarely need to navigate to /sparkhistory/ independently.
Accessing platform tools
Platform tools are accessible from the Platform Tools section at the bottom of the Console sidebar. Each tool can be opened embedded within the Console or in a new browser tab using the external link icon.
If a tool is not visible in your sidebar, either your role does not grant access or the tool is not enabled in your deployment. Contact your Granica administrator to request access.
Configure Crunch
System-wide platform settings that control how Granica Crunch operates, calculates savings, and communicates with your team.
Connect Query History
Next Page