Dell PowerProtect Data Manager extension
- Latest Dynatrace
- Extension
Ingest metrics, activities, and other logs from PowerProtect Data Manager.
Get started
Overview
PowerProtect Data Manager is a data protection software designed to secure modern workloads including backups, dev/test re-use, protecting cloud native applications, centralized governance and control, and self-service backup and restore.
Use the Dynatrace Dell PowerProtect Data Manager extension to collect performance and health data about your PowerProtect Data Manager deployment and get insights into activities, alerts, and audit logs.
Use cases
- Monitor overall system health to identify issues that can affect performance or reliability
- Monitor configuration changes
- Extract Dynatrace problem events from PowerProtect alert or health issue records
- Monitor the states of your storage systems
Requirements
-
A PowerProtect instance with the PowerProtect Data Manager REST API reachable from ActiveGates
-
A user with the "User" or "readonly" role
Compatibility information
This extension uses the PowerProtect Data Manager REST API.
Activation and setup
Find Dell PowerProtect Data Manager in the in-product Extensions or Hub page and activate it. If offline, you can download the extension from the Hub page in the Versions section and install as a custom extension.
Monitoring configuration
Once the extension is activated in your environment, you can create monitoring configurations. Each monitoring configuration can have one PowerProtect instance.
-
Select the desired ActiveGate group that will run the monitoring configuration.
- Host
- Authentication
- Username & password (credential vault is supported)
- Verify SSL (can be disabled if monitoring a local instance with a self-signed certificate)
- Activities
- Collection interval (0 to disable)
- Collect failed job group activites
- Collect completed with warnings job group activites
- Audit logs
- Collection interval (0 to disable)
- System issues
- Collection interval (0 to disable)
- Alerts
- Collection interval (0 to disable)
- Collect warning severity alerts (in addition to critical)
- Filter by time
- If Filter by time is disabled, reporting will be based on the "acknowledgement" state of the alert within PowerProtect. So this will result in any unacknowledged alerts continuing to be reported (can be used to keep extracted problems open).
- If Filter by time is enabled, we will only report alerts that occurred during that monitoring interval (based on the postedTime of the alert).
- Log level
-
Metrics
Review the list of feature sets to see which metrics are collected. Metrics are related to the overall system health and storage system statuses.
-
Log events
Many types of records from PowerProtect are ingested into Dynatrace in the form of log events. These log events can be manually reviewed as well as used in log event extraction and metric configurations. The following types of records can be ingested:
-
An activity represents a long running asynchronous execution in the system. It can represent a group of jobs, a single job, or a single task. These will have a 'record_type' attribute of 'activity'.
-
Audit log tracks configuration modification activity from users. These will have a 'record_type' attribute of 'audit_log'.
-
An issue affecting the health of the PowerProtect system. These events can affect the overall system health score. These will have a 'record_type' attribute of 'system_health_issue'.
-
Alerts enable you to track the performance of data protection operations in PowerProtect Data Manager so that you can determine whether there is compliance to service level objectives. These will have a 'record_type' attribute of 'alert'.
-
-
Log processing rules
One log processing rule is included that will extract and create a new column (vm.name) from log events for patterns of logs that include a virtual machine name in their content.
Details
Licensing and costs
There is no charge to use the extension. You are only charged for the data that the extension ingests.
The Dell PowerProtect Data Manager extension ingests custom metrics, which consume Davis Data Units (DDUs) (Dynatrace classic license) or Metrics powered by Grail (DPS), according to your license model.
Assuming all feature sets are enabled, the approximate number of metric data points per minute is:
15 + <number of protection engine proxies>
The number of reported log records will be based on how many audit logs, activities, alerts, and system health issues occur.
Dynatrace Platform Subscription
In the Dynatrace Platform Subscription, metric ingestion consumes Metrics powered by Grail according to the number of ingested metric data points.
To calculate the approximate yearly consumption, apply the following calculation: <metric data points per minute> * 60 minutes * 24 hours * 365 days.
For logs, regular consumption applies. See Log Analytics.
Dynatrace classic license
In the classic licensing model, metric ingestion consumes 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.
For logs, regular DDU consumption applies. See DDU consumption for Log Management and Analytics or DDUs for Log Monitoring Classic.
The DDU cost above does not include any possible log events or custom events that are triggered by the extension. For more information, see DDU events.
Feature sets
When activating your extension using a monitoring configuration, you can limit monitoring to one of the feature sets. To work properly, the extension has to collect at least one metric after the activation.
In highly segmented networks, feature sets can reflect the segments of your environment. Then, when you create a monitoring configuration, you can select a feature set and a corresponding ActiveGate group that can connect to this particular segment.
All metrics that aren't categorized into any feature set are considered to be the default and are always reported.
A metric inherits the feature set of a subgroup, which in turn inherits the feature set of a group. Also, the feature set defined on the metric level overrides the feature set defined on the subgroup level, which in turn overrides the feature set defined on the group level.
default
| Metric name | Metric key | Description |
|---|---|---|
| Availability | ppdm.availability | Indicates the availability of the Power Protect Data Manager instance as a percentage |
| System health score | ppdm.system_health.score | Numerical health score of the Power Protect Data Manager system (0-100) |
| System health status | ppdm.system_health.status | Overall health status of the Power Protect Data Manager system (GOOD, FAIR, or POOR) |
| System health category score | ppdm.system_health.category.score | Health score for a specific health category (0-100) |
| System health category status | ppdm.system_health.category.status | Health status for a specific category (1 sample per status value) |
| System health category issues | ppdm.system_health.category.issues | Number of issues in a specific health category |
| Critical alert count | ppdm.alert.critical | Number of critical alerts grouped by acknowledged state |
| Warning alert count | ppdm.alert.warning | Number of warning alerts grouped by acknowledged state |
| Informational alert count | ppdm.alert.informational | Number of informational alerts grouped by acknowledged state |
storage-systems
| Metric name | Metric key | Description |
|---|---|---|
| Storage system status count (fair) | ppdm.storage.summary.fair | Number of storage systems with a FAIR health status |
| Storage system status count (good) | ppdm.storage.summary.good | Number of storage systems with a GOOD health status |
| Storage system status count (poor) | ppdm.storage.summary.poor | Number of storage systems with a POOR health status |
| Storage system status count (total) | ppdm.storage.summary.total | Total number of storage systems monitored |
| Storage system total capacity | ppdm.storage.capacity.total_bytes | Total physical capacity of the storage system |
| Storage system used capacity | ppdm.storage.capacity.used_bytes | Used physical capacity of the storage system |
| Storage system free capacity | ppdm.storage.capacity.free_bytes | Free physical capacity of the storage system |
| Storage system capacity utilization | ppdm.storage.capacity.percent_used | Percentage of physical capacity used on the storage system |
| Storage system readiness | ppdm.storage_system.readiness | Readiness state of the storage system (1 sample per state value) |
assets
| Metric name | Metric key | Description |
|---|---|---|
| Protected asset count | ppdm.assets.protected | Number of assets in PROTECTED status grouped by asset type |
| Unprotected asset count | ppdm.assets.unprotected | Number of assets in UNPROTECTED status grouped by asset type |
| Excluded asset count | ppdm.assets.excluded | Number of assets in EXCLUDED status grouped by asset type |
| Total asset count | ppdm.assets.total | Total number of assets grouped by asset type |
| Protected asset size | ppdm.assets.protected.size_bytes | Total size in bytes of protected assets grouped by asset type |
| Total asset size | ppdm.assets.total.size_bytes | Total size in bytes of all assets grouped by asset type |
| Total policy count | ppdm.policy.total | Total number of protection policies grouped by asset type |
| Active policy count | ppdm.policy.active | Number of enabled protection policies grouped by asset type |
| Disabled policy count | ppdm.policy.disabled | Number of disabled protection policies grouped by asset type |
| Inventory source last discovery result | ppdm.inventory_source.last_discovery_result | Last discovery result status per inventory source (state metric; dims source_name, source_type, status) |
| Inventory source discovery age | ppdm.inventory_source.discovery_age_seconds | Seconds since the last successful discovery of an inventory source |
protection-engine-proxies
| Metric name | Metric key | Description |
|---|---|---|
| Protection Engine Proxy Status | ppdm.protection_engine.proxy.status | Status of individual protection engine proxies used for data protection operations |
jobs
| Metric name | Metric key | Description |
|---|---|---|
| Activity count | ppdm.activity | Count of backup/restore/replicate activity records (1 per activity, split by class type, status, and category) |
| Jobs running | ppdm.jobs.running | Number of currently running jobs (dim category) |
| Jobs queued | ppdm.jobs.queued | Number of queued jobs (dim category) |
| Jobs completed | ppdm.jobs.completed | Number of completed jobs (dim category) |
| Jobs OK | ppdm.jobs.ok | Number of jobs that completed successfully (dim category) |
| Jobs failed | ppdm.jobs.failed | Number of failed jobs (dim category) |
| Jobs OK with errors | ppdm.jobs.ok_with_errors | Number of jobs completed with errors (dim category) |
| Jobs canceled | ppdm.jobs.canceled | Number of canceled jobs (dim category) |
| Jobs skipped | ppdm.jobs.skipped | Number of skipped jobs (dim category) |
| Jobs unknown | ppdm.jobs.unknown | Number of jobs with unknown status (dim category) |
storage-units
| Metric name | Metric key | Description |
|---|---|---|
| Storage unit total capacity | ppdm.storage_unit.capacity.total_bytes | Total capacity of the storage unit (MTree) |
| Storage unit used capacity | ppdm.storage_unit.capacity.used_bytes | Used capacity of the storage unit (MTree) |
| Storage unit free capacity | ppdm.storage_unit.capacity.free_bytes | Free (available) capacity of the storage unit (MTree) |
| Storage unit capacity utilization | ppdm.storage_unit.capacity.percent_used | Percentage of capacity used on the storage unit (MTree) |
| Storage unit status | ppdm.storage_unit.status | Discovery status of the storage unit (1 sample per status value) |
search-clusters
| Metric name | Metric key | Description |
|---|---|---|
| Search cluster status | ppdm.search_cluster.status | Operational state of the search cluster (1 sample per state value) |
| Search cluster total nodes | ppdm.search_cluster.nodes.total | Total number of nodes in the search cluster |
| Search cluster online nodes | ppdm.search_cluster.nodes.online | Number of online (non-failed) nodes in the search cluster |
| Search cluster offline nodes | ppdm.search_cluster.nodes.offline | Number of failed/offline nodes in the search cluster |
| Search cluster node status | ppdm.search_cluster.node.status | Status of an individual search cluster node (1 sample per node per status) |
protection-engines
| Metric name | Metric key | Description |
|---|---|---|
| Protection engine status | ppdm.engine.status | Operational status of a protection engine (1 sample per status) |
| Protection engine ready proxies | ppdm.engine.proxies.ready | Number of ready proxies on the protection engine |
| Protection engine failed proxies | ppdm.engine.proxies.failed | Number of failed proxies on the protection engine |
| Protection engine disabled proxies | ppdm.engine.proxies.disabled | Number of disabled proxies on the protection engine |
| Protection engine protected VMs | ppdm.engine.protected.vms | Number of VMs protected by the protection engine |
| Protection engine protected size | ppdm.engine.protected.size_bytes | Total protected size in bytes for the protection engine |
