Platform operations and environment management
Console boundaries
LifeTime is the cross-environment control plane: you register environments, deploy applications, manage platform users, and read Environment Health. Service Center is the per-environment administration console: logs, timers, integrations, security policies, and module-level settings. Service Studio is the IDE, and 1-Click Publish only targets the environment you are connected to.
Operating rules
- Register every environment in LifeTime and keep the controller, front-end, and database topology documented.
- Use Environment Health as a triage dashboard: it aggregates errors, performance, security, database, cache, scheduler, email, and integrations, but it is not a full APM.
- Manage users at the right layer: LifeTime roles for platform administration and deployment; Service Center policies for authentication and session behavior.
- Change log levels deliberately; verbose logging increases I/O and can mask the original symptom.
Worked example
Production Environment Health shows the Errors indicator red. You open Service Center > Logs > Error Log, filter by module, and find repeated integration timeouts in one module. You check the integration log for the endpoint and confirm a third-party latency spike, not a platform fault. You raise the timeout only after confirming the endpoint SLA, then monitor the error rate in Environment Health.
Traps
- Opening Service Center to deploy across environments instead of using LifeTime.
- Treating Environment Health as complete monitoring and skipping log correlation.
- Changing security or session policy in one environment and assuming it propagates.
- Forgetting that Service Center settings are environment-specific.