📖 How to use Optimiser Cloud-Logs

✕

Optimiser Cloud-Logs is a secure, audited web terminal for reaching the servers you're allowed to work on — straight from your browser, with no SSH keys to manage. This guide covers the everyday basics for developers.

1. Getting started

• After login you land on the Available Servers list. Use the search box to filter.
• Click a server to open a live terminal to it. The top bar shows which server you're on.
• Use ← Servers (top-right) to go back and switch to another server. You can open more servers in new browser tabs.

2. Terminal basics

• Type a command and press Enter to run it.
• ↑ / ↓ — scroll through your command history. Tab — auto-complete files/paths.
• Ctrl+C — stop the current command (e.g. a running log stream).
• Copy: select text, then Ctrl+Shift+C. Paste: Ctrl+V or right-click.
• Full-screen tools (vi, less, top) run normally — press their own quit keys (e.g. q, or :q in vi) to exit.

3. Monitoring your apps with PM2

If your apps run under PM2, these read-only commands are the day-to-day toolkit:

Actions that change state (pm2 restart, stop, delete, etc.) may be restricted by your role — if one is blocked, that's policy, not a bug.

4. Editing files

• If file editing is enabled for you, vi <file> (or sudo vi <file>) opens the file right in the terminal.
• Basic vi: i to insert, Esc to stop editing, :wq to save & quit, :q! to quit without saving.

5. 🔴 Everything is recorded

• Every command, your keystrokes, and the full session (input & output) are recorded and kept for audit. The red “Session is being recorded” badge is always shown.
• Sensitive values in output (passwords, keys, tokens) may be automatically masked — please don't try to work around masking.
• Work professionally, as you would on any production system.

6. Your access & getting more

• You can only reach the servers assigned to you and run the commands your role permits.
• If a command is refused (“not permitted”, “blocked by policy”), that's your access level — not an error.
• Need elevated access — a blocked command, sudo, more servers, or file-edit rights? Contact your Admin / DevOps team and they can grant it to your account or role.

7. Good to know

• Auto-logout: after a period of inactivity (1 hour by default, or the time set for you) you're signed out of all tabs and must log in again.
• Session sharing: if enabled for you, use ⇄ Share in the terminal to let a teammate watch live and take over. (Ask an admin to enable it if you don't see the button.)
• Stuck line? If a typed command won't clear, press Ctrl+U or Ctrl+C to reset it.

Questions or access requests → your Admin / DevOps team.

Got it

⇄ Share this session

✕

Link stays active for

Share this link