SVIEW — Overview
SVIEW is the PushOps self-service portal. It is where your team manages
everything day to day — provisioning databases and caches, configuring
deployments, requesting access, and viewing health, costs, and compliance
reports.
Navigation
The left-hand sidebar is organized around the Environment / Service / Component
hierarchy described in Key Concepts.
| Area | What it gives you |
|---|---|
| Environments | Top-level dashboard — health, stage, and cloud per Environment |
| Services | Logical groups of Components within an Environment |
| Catalog | Provision new Components (databases, caches, queues, storage, apps) |
| Access Requests | Request and approve short-lived infrastructure access |
| Audit Logs | History of actions taken on the platform |
| Costs | Spend breakdown by namespace |
| Reports | Node utilisation and compliance reports |
| Health check | Cross-Environment service health overview |
Clicking into an Environment shows its Services; clicking into a Service
shows its Components. Each Component has its own dashboard with configuration,
secrets, variables, and status.
Provisioning something new
New databases, caches, queues, and other resources are created from the
Catalog. The Catalog lists the available Component types by category and
cloud provider. Select a type, fill in the configuration, and the platform
provisions it — no cloud-console access is needed.
For data services specifically, see Data Services.
What requires a support request
Some things are not yet self-service — creating a new Environment or namespace,
for example. Raise those in your dedicated Slack channel.
If you are not sure whether something is self-service, check What You Can Do
vs. What We Manage first.
Related articles
- Key Concepts — the definitions behind the hierarchy
- Environments — the Environments dashboard in detail
- Data Services — provisioning databases, caches, and queues
Updated about 5 hours ago