In this guide
Before you start
Sign in with the account that owns the resource. Identify the service you intend to inspect before running an action.
Step-by-step workflow
- Find the service
Open the resource area for the relevant runtime and select the service. Confirm its identity before running a lifecycle action.
- Inspect before changing
Review current state, configuration and any pending operations. Use the available logs or console to investigate application problems.
- Follow the operation
Review the requested action and its confirmation. Follow the operation until it completes, then check the application's behavior.
- Review usage
Compare usage and estimates with the selected offer. Use issued invoices for billed amounts and budget alerts to monitor spending.
Resources and services
Use the virtual machine, container or function area to find your workload. The detail view shows the service state and actions available for that resource. A submitted lifecycle request may need time to complete; inspect its resulting state.
Access and operations
Use the console tools supported by your service. Guest credentials and application access remain separate from the platform session. Cloud Shell is an authenticated workspace with its own availability and session policy.
Connections
Networking views expose supported networks, subnets, routes and firewall configuration. Review actual service reachability after changing a network rule.
Billing and budgets
The billing console provides usage and cost estimates alongside issued invoices. Budget alerts monitor spending; they do not stop resources or enforce a hard cap. Review the underlying offer before changing a configuration.
Check your result
You can locate service configuration, follow an operation and find the relevant billing information without confusing guest access with platform access.
If something does not work
If an action is unavailable, check the service state and account permissions. A pending operation may need to complete before a conflicting action becomes available.
- An action is disabled
- Check the resource state, pending operations and your permissions. Avoid repeating conflicting requests.
- A budget alert fired
- Review the services driving usage and choose the appropriate response. Alerts do not stop services or enforce a spending cap.