Skip to technology filters Skip to main content
Dynatrace Hub

Extend the platform,
empower your team.

Popular searches:
Home hero bg
HPE Integrated Lights-Out (iLO)HPE Integrated Lights-Out (iLO)
HPE Integrated Lights-Out (iLO)

HPE Integrated Lights-Out (iLO)

Remotely collect iLO data via the Redfish API.

Extension
Free trial
Gen3 dashboard showing monitored iLO hosts.First set of metrics on the iLO entity. Shows a log record.Expanded properties of the iLO host.Portion of the iLO entity screen showing additional metrics.
  • Product information
  • Release notes

Overview

Integrated Lights-Out (iLO) is a proprietary management technology built into HPE products that allows for remote control access to ProLiant servers even without being connected to the main network. The iLO extension allows for remote monitoring of such instances via their Redfish API (first introduced in iLO 4).

Use cases

  • Monitor iLO instance health and availability
  • Quickly alert on health or availability related issues
  • View and alert on instance activity such as logins, virtual power events, log clears, and some configuration changes

Get started

Requirements

  • Minimum Dynatrace environment and ActiveGate version 1.310
    • ActiveGate must be able to reach the target iLO instances (HTTPS)
  • An OS in the listed of the supported distributions
  • A user account on the iLO instance with at least ReadOnly permissions (username:password)

Dynatrace configuration

Find 'HPE Integrated Lights-Out (iLO)' in the in-product Extensions App or Hub page and activate (if offline you can download the extension from this Hub page in the 'Release notes' section and install as a custom extension).

Monitoring configurations

Once activated in your environment you can create monitoring configurations. Each monitoring configuration can have one or more iLO targets.

First select the desired ActiveGate group that will run the monitoring configuration.

For each cluster configure onr or more iLO hosts:

  • Default authentication

    • If you are using the same credentials for multiple hosts you cand define top-level authentication that will apply to all endpoints (unless overridden at the endpoint level)
    • Can use the credential vault

  • Endpoints

    • iLO Host: hostname or IP address to connect to
      • If the port is left off then the default 443 will be used. If you need to use a custom port add it at the end of the host name (e.g. <hostname>:<port>)
    • Alias (Optional): if an alias is configured it will override any auto-discovery of the hostname. If not set, we will try to determine the configured hostname based on the Redfish API output and will fall back to the configured hostname or IP address
      • Issues have been observed with the discovered names reverting to previous values after resets and other issues. If you want to ensure the entity name is consistent and what you expect you should use the alias configuration
    • Credentials: Username and password pair. This can come from the Credential Vault (make sure the credential (username/password) was enabled for use with extensions)

  • Collect iLO Event Logs (IEL)

  • Log collection delay (if logs enabled): How far back to shift log collection windows to ensure that ther are log records available in the queried window

    • There is a delay after an event occurs before a log is available to view/collect. To ensure we don't query logs 'to soon' we shift back the query timeframe to a time when we can be sure the logs will be available. For example, with the default delay of 60 minutes at 10:00 we will query for logs from 8:59 to 9:00.

  • Advanced settings:

    • Use log collection time as timestamp
      • By default we will use the true event timestamp as the timestamp for the log ingested into Dynatrace. Because a delay is required during collection this means that the most recent periods (1 hour by default) will not have records. If you prefer, you can enable this to have the collection time used as the timestamp associated with the log record. This will result in the records 'appearing' to be occurring after their true time but will ensure you have records in the recent intervals regardless of the configured collection delay
    • Connection retries: default 5
    • Connection timeout: default 20 seconds
    • Collection frequency: default 1 minute
    • Task bucket size: up to 500 instances can be configured per monitoring configuration but you can break this up into multiple smaller tasks (or batches) that can be distributed across ActiveGates in the group

  • Log level

Details

Metrics

Review the list of feature sets to see which metrics are collected. Note that different supported iLO versions have significant changes in their Redfish API output which means that some versions (typically the earlier iLO 4) will have much less data exposed for collection meaning monitoring of such instances will be more limited than the later version(s). As such, not every metric in the available feature sets will be reported for all instances.

Log events

If enabled, we will collect iLO Event Log (IEL) records. There is a significant delay before such records are guaranteed to be avaialble for collection so by default there is a 1 hour collection delay. You can lower this delay but make sure to verify that you are not losing records by querying too soon. The API delay for log availability has been observed to mirror the delay before they are avaialble in the iLO management UI log viewer.

Compatibility information

  • iLO 4
  • iLO 5
  • iLO 6 (limited testing)

iLO 4 was the first version with the Redfish API and as such reports a much smaller amount of data as compared to later versions, primarily limited to instance properties and high-level health statuses.

iLO 6 has been tested to a limited extent but has not been confirmed to have run on a live iLO 6 instance. While safe to use, if you experience issues or feel something is missing reach out to support to help us better cover this latest version.

Troubleshooting

The most likely issue is that the configuration does not point to the Redfish API endpoint on the instance or that the instance is unreachable from the configured ActiveGate(s). To manually test the configured target, reachability from the ActiveGate, and credentials you can run a curl command like below (see the iLO doc) for details.

For the most accurate test it must be run from the ActiveGate the extension will try to connect from (or an ActiveGate in the group).

curl --include --insecure     \
     --user username:password \
     --location https://{IP}/redfish/v1/Systems/

Licensing

Metrics

License consumption is based on the number of metric data points ingested. The following formula will provide approximate annual data points ingested assuming all feature sets are enabled. Also note that due to the lower amount of data available in earlier iLO versions usage in iLO 4 will be lower than iLO 5. These numbers estimate the 'maximum' usage.

(24 + <number_of_logical_drives> + (2 * <number_of_fans>) + <number_of_processors> + <number_of_storage_drives>) * 60 minutes * 24 hours * 365 days data points per year

Classic licensing

In the classic licensing model, metric ingestion will consume Davis Data Units (DDUs) at the rate of .001 DDUs per metric data point.

Multiply the above formula for annual data points by .001 to estimate annual DDU usage.

Log records

Each iLO Event Log record will be ingested as a log record.

Log management and analytics (powered by Grail)

License consumption is based on the size (in bytes) of data ingested & processed, retained, and queried so there is not a single formula to estimate the total consumption from this extension. Consult the log management and analytics documentation for details on the other dimensions that will effect license consumption.

Classic licensing

In the classic licensing model, log record ingestion will consume Davis Data Units (DDUs) at the rate of 100 DDUs per Gigabyte of log records ingested.

Log monitoring classic

In log monitoring classic, license consumption is based on the number of ingested log records.

Classic licensing

In the classic licensing model, log record ingestion will consume Davis Data Units (DDUs) at the rate of .0005 DDUs per ingested log record.

Multiply estimated ingested log records by .0005 to estimate DDU usage from log records.

Dynatrace
By Dynatrace
Dynatrace support center
Subscribe to new releases
Copy to clipboard

Extension content

Content typeNumber of items included
screen logs cards
1
document dashboard
1
dashboards
1
screen layout
1
list screen layout
1
screen entities lists
1
generic type
1
screen chart groups
10
metric metadata
30

Feature sets

Below is a complete list of the feature sets provided in this version. To ensure a good fit for your needs, individual feature sets can be activated and deactivated by your administrator during configuration.

Feature setsNumber of metrics included
Metric nameMetric keyDescriptionUnit
Graphical console enabledhp.ilo.manager.graphical_console_enabledIndicates whether the graphical console is enabled or notState
Metric nameMetric keyDescriptionUnit
Availabilityhp.ilo.availabilityThe ability to connect and login to the iLO instancePercent
Aggregate server healthhp.ilo.health_status.aggregate_server_healthOverall health stateState
Metric nameMetric keyDescriptionUnit
Total system memoryhp.ilo.memory.total_system_memoryTotal system memoryGibiByte
Power on timehp.ilo.uptimePower on time/uptime as reported by the APISecond
CPU utilizationhp.ilo.cpu_utilReported CPU utilizationPercent
I/O bus utilizationhp.ilo.io_bus_utilInput/output bus utilizationPercent
Memory bus utilizationhp.ilo.memory_bus_utilMemory bus utilizationPercent
BIOS or hardware healthhp.ilo.health_status.bios_or_hardware_healthBIOS or hardware healthState
Fan healthhp.ilo.health_status.fansFan healthState
Fans redundancyhp.ilo.health_status.fans_redundancyIndicates whether the fans are redundant or notState
Memory healthhp.ilo.health_status.memoryMemory healthState
Network healthhp.ilo.health_status.networkNetwork healthState
Power supply healthhp.ilo.health_status.power_suppliesPower supply healthState
Power supply redundancyhp.ilo.health_status.power_supplies_redundancyIndicates whether power supplies are redundantState
Processor healthhp.ilo.health_status.processorsOverall processor(s) health statusState
Temperature healthhp.ilo.health_status.temperaturesTemperature healthState
Smart storage battery healthhp.ilo.health_status.smart_storage_batterySmart storage battery health (iLO 5)State
Smart storage logical drive capacityhp.ilo.smart_storage.logical_drive.capacitySmart storage logical drive capacity (iLO 5)GigaByte
Metric nameMetric keyDescriptionUnit
Chassis healthhp.ilo.chassis.healthOverall chassis healthState
Chassis power supply healthhp.ilo.chassis.power_supply.healthChassis power supply healthState
Chassis tempertature healthhp.ilo.chassis.temperature.healthChassis temperature healthState
Chassis tempertature readinghp.ilo.chassis.temperature.readingCurrent chassis temperature readingCount
Chassis fan healthhp.ilo.chassis.fan.healthChassis fan healthState
Chassis fan readinghp.ilo.chassis.fan.readingCurrent chassis fan temperature readingCount
Chassis power supply redundancyhp.ilo.chassis.power_supply_redundancy_healthIndicates whether the chassis power supply is redundant or notState
Chassis smart storage battery healthhp.ilo.chassis.smart_storage_battery.healthChassis smart storage battery health (iLO 5)State
Chassis smart storage battery charge levelhp.ilo.chassis.smart_storage_battery.charge_level_percentChassis smart storage battery charge level (iLO 5)Percent
Metric nameMetric keyDescriptionUnit
Drive healthhp.ilo.storage.drive.healthIndividual storage drive healthState
Metric nameMetric keyDescriptionUnit
Processor healthhp.ilo.processor.healthIndividual processor healthState

Full version history

To have more information on how to install the downloaded package, please follow the instructions on this page.
ReleaseDate

Full version history

  • Initial version including packaging error fix
Dynatrace Hub
Get data into DynatraceBuild your own app
All (768)Log Management and AnalyticsKubernetesAI and LLM ObservabilityInfrastructure ObservabilitySoftware DeliveryApplication ObservabilityApplication SecurityDigital ExperienceBusiness Analytics
Filter
Type
Built and maintained by
Deployment model
SaaS
  • SaaS
  • Managed
Partner FinderBecome a partnerDynatrace Developer

Discover recent additions to Dynatrace

Problems logo

Problems

Analyze abnormal system behavior and performance problems detected by Davis AI.

Logs logo

Logs

Explore all your logs without writing a single query.

Security Investigator logo

Security Investigator

Fast and precise forensics for security and logs on Grail data with DQL queries.

Business Flow logo

Business Flow

Track, analyze, and optimize your critical business processes.

Cost & Carbon Optimization logo

Cost & Carbon Optimization

Track, analyze, and optimize your IT carbon footprint and public cloud costs.

Davis Anomaly Detection logo

Davis Anomaly Detection

Detect anomalies in timeseries using the Davis AI

Analyze your data

Understand your data better with deep insights and clear visualizations.

Notebooks logo

Notebooks

Create powerful, data-driven documents for custom analytics and collaboration.

Dashboards logo

Dashboards

Transform complex data into clear visualizations with custom dashboards.

Automate your processes

Turn data and answers into actions, securely, and at scale.

Workflows logo

Workflows

Automate tasks in your IT landscape, remediate problems, and visualize processes

Jira logo

Jira

Create, query, comment, transition, and resolve Jira tickets within workflows.

Slack logo

Slack

Automate Slack messaging for security incidents, attacks, remediation, and more.

Secure your cloud application

See vulnerabilities and attacks in your environment.

Security Overview logo

Security Overview

Get a comprehensive overview of the security of your applications.

Code-Level Vulnerabilities logo

Code-Level Vulnerabilities

Detect vulnerabilities in your code in real time.

Threats & Exploits logo

Threats & Exploits

Understand, triage, and investigate application security findings and alerts.

Are you looking for something different?

We have hundreds of apps, extensions, and other technologies to customize your environment

Leverage our newest innovations of Dynatrace Saas

Kick-start your app creation

Kick-start your app creation

Whether you’re a beginner or a pro, Dynatrace Developer has the tools and support you need to create incredible apps with minimal effort.
Go to Dynatrace Developer
Upgrading from Dynatrace Managed to SaaS

Upgrading from Dynatrace Managed to SaaS

Drive innovation, speed, and agility in your organization by seamlessly and securely upgrading.
Learn More
Log Management and Analytics

Log Management and Analytics

Innovate faster and more efficiently with unified log management and log analytics for actionable insights and automation.
Learn more