This guide provides a step-by-step, hands-on setup walkthrough for getting OpsRamp up and running in your environment. If you’re a platform administrator, operator, or implementation engineer, this is the place to begin your technical onboarding.

For a high-level understanding of OpsRamp features, roles, and navigation paths, refer to Start Your OpsRamp Journey.

By following this guide, you will:

  • Access your OpsRamp instance
  • Create a tenant (client) account
  • Install and verify the OpsRamp agent
  • Apply monitoring templates
  • Visualize dashboards and validate alert generation

This guide assumes you already have a provisioned OpsRamp account and Partner Administrator credentials.


1. Log in to the OpsRamp Platform

Direct Login (Standalone)

  1. Open your browser and go to:
    https://{your-org}.app.opsramp.com
  2. Enter your credentials and log in as a Partner Administrator.
  3. You’ll be directed to the OpsRamp console.

Via HPE GreenLake (Optional)

  • Sign in to the HPE GreenLake portal.
  • Click on the OpsRamp tile.
  • You will be redirected to your provisioned OpsRamp environment.
2. Create a Client Account

OpsRamp uses a multi-tenant model. Each logical business unit, department, or customer (if you’re an MSP) should be mapped as a client account.

  1. Navigate to: Setup → Accounts → Clients
  2. Click + Add and fill in the following fields:
FieldDescription
Client NameDisplay name of the tenant organization or unit.
AddressMain office address (for reports and metadata).
CountryUsed for localization and compliance settings.
Time ZoneEnsures timestamps in alerts, reports, and dashboards are accurate.
  1. Set Auto Monitoring Resources to No to configure monitors manually.
  2. Click Next, then Finish.

The Client Details page opens with further configuration options.

3. Install the OpsRamp Agent

The OpsRamp agent is a lightweight software component installed on your target systems to enable data collection, remote actions, and availability monitoring.

OpsRamp Agent Capabilities:

  • Collects metrics, logs, and alerts
  • Executes remediation workflows
  • Enables secure communication with OpsRamp

To install the agent:

  1. Go to: Setup → Account → Integrations
  2. Select your OS:
  3. Copy the provided installation command (auto-generated for your client + org ID).
  4. Log in to the server and run the command with root/admin rights.

Verify Agent Status:

  1. Navigate to: Infrastructure → Resources → Servers
  2. Locate your resource by name or IP.
    The status may show Undefined until a monitor is assigned.
4. Apply Monitoring Templates

Monitoring templates define the metrics, thresholds, and collection intervals for different types of infrastructure.

Assign a Monitoring Template:

  1. Go to: Setup → Monitoring → Templates
  2. Use the filter/search bar to find a template (e.g., Windows Server, MySQL, Apache).
  3. Click the template and choose Assign.
  4. Select the client and target resources.
  5. Click Submit.

You can also create custom templates for specialized monitoring use cases.

5. View Dashboards

Dashboards help visualize real-time performance data and alerts across your infrastructure.

View the Default Dashboard:

  1. Navigate to: Dashboards → Dashboards 2.0
  2. Select the default dashboard. You’ll see:
    • Resource availability
    • CPU and memory trends
    • Top alerts by severity
    • Resource inventory breakdown

Customize Your Dashboard:

  1. Click + Add Dashboard
  2. Add widgets such as:
    • Metric graphs
    • Top N alerts
    • Resource availability by site
  3. Save and share with specific roles or accounts.
6. Generate and Review Alerts

Simulate an Alert:

  1. Power off a server with the OpsRamp agent installed.
  2. Wait ~5 minutes.
  3. Go to: Command Center → Alerts
  4. Search or filter by resource or client.
    You should see a Critical alert titled OpsRamp Agent is Offline.

Clear the Alert:

  1. Power the server back on.
  2. The alert should auto-resolve and change from Critical → OK.

Alerts are retained for historical review and post-incident analysis.