If your organization has feature-based licenses, the Metering page displays information based on your licenses.
The Metering page displays the following views depending on the licensed features:
Dashboard view
If you have the appropriate licenses, the Metering page displays information in a dashboard view.
The Metrics Summary This Month area shows the total computing resources remaining for the month and each meter type. You can also display a table of all meters that apply to your organization, depending on your organization’s editions.
The detail area for each meter type displays metering information for the month, including resource amounts remaining, average resource usage per day, and days of usage remaining. To see more detail for a meter type, you can display a detail chart that shows usage by organization or sub-organization, date range, and runtime environment.
License Metrics view
If you do not have the licenses required to see the dashboard view, the Metering page displays license metrics in a table. The table lists summary metrics for all meters that apply to your organization, which is determined by your organization’s editions.
You can also navigate to the License Metrics view for all meters from the summary area in the dashboard view.
Note: Feature-based licensing is different from IPU-based licensing. IPUs are not used for feature-based licenses. If your organization uses IPUs, see Informatica processing unit metrics.
Viewing license metrics
You can view a table of all meters used in your organization. For some meters, you can download a report that shows the metering usage. View the table and download the report from the License Metrics view of the Metering page.
To open the License Metrics view from the dashboard view, click All Meters in the Metrics Summary This Month area. If you do not have the licenses required to see the dashboard view, the License Metrics view is displayed when you open the Metering page.
The meters that appear in the License Metrics view are determined by the editions that your organization has. Your organization might also be assigned custom meters. Metering information might not be available for every edition.
If your organization has multiple editions or uses custom meters, a meter might be displayed multiple times with different limits. In this case, the least restrictive limit applies. For example, if one edition has a limit of 500 synchronization jobs per day and another edition has a limit of 100 synchronization jobs per day, the 500 job per day limit applies. The In Effect column indicates which limit applies.
The License Metrics view displays the following information for each meter:
Property
Description
Edition
Name of the edition that is associated with the meter.
Service
Service to which the meter applies.
Metering
Name of the meter. For example, the number of synchronization jobs per day, the number of rows processed by mapping jobs per month, or the total number of replication jobs. For Mass Ingestion, this column shows the ingestion type: Mass Ingestion Files, Mass Ingestion Applications, Mass Ingestion Databases, Mass Ingestion Applications - Change Data Capture, Mass Ingestion Databases - Change Data Capture, and Mass Ingestion Streaming.
Limit
Numeric limit such as the maximum number of jobs or processed rows.
The limit applies to the parent organization and to each sub-organization. For example, if the limit is 100 jobs per day, users in the parent organization can run 100 jobs per day, and users in each sub-organization can also run 100 jobs per day.
If this field displays -1, there is no limit.
Used
The actual number units consumed, such as the number of jobs run or compute hours used, in the organization or sub-organization during the metering period.
Percent Used
The percentage of units consumed in the organization or sub-organization during the metering period.
In Effect
Indicates whether the meter is in effect for the organization or sub-organization.
Meter definitions
The meters that appear in the License Metrics view of the Metering page are determined by the editions that your organization has.
The following table describes the meters that might be in effect based on your editions:
Meter
Definition
Advanced Data Integration
Compute units measured in hours for mappings in advanced mode.
Advanced Data Integration with Advanced Serverless
Serverless compute units measured in hours for mappings in advanced mode.
Advanced Data Quality
Compute units measured in hours for data quality assets in mappings in advanced mode.
Advanced Data Quality with Advanced Serverless
Serverless compute units measured in hours for data quality assets in mappings in advanced mode.
CDI Rows Processed
Number of rows processed by mappings outside of advanced mode.
CDI-E Compute Hours
Deprecated. This meter has been replaced with the Advanced Data Integration meter.
Daily/monthly incoming API request maximum
Number of API access requests per day or per month.
Data Integration with Advanced Serverless
Serverless compute units measured in hours for mappings outside of advanced mode.
Data Quality
Compute units measured in hours for data quality assets in mappings outside of advanced mode.
Data Quality with Advanced Serverless
Serverless compute units measured in hours for data quality assets in mappings outside of advanced mode.
Mass Ingestion meters
For Mass Ingestion Applications, Mass Ingestion Databases, Mass Ingestion Files, and Mass Ingestion Streaming, the number of gigabytes (GBs) ingested by application ingestion, database ingestion, file ingestion, or streaming ingestion jobs per month. For Mass Ingestion Applications - Change Data Capture and Mass Ingestion Databases - Change Data Capture, the number of rows ingested.
Taskflow Runs
Number of taskflow runs per day or per month.
Number of PowerCenter jobs per day/month
Number of PowerCenter jobs per day or per month.
Number of mapping jobs per day/month
Number of mapping jobs per day or per month.*
Number of masking jobs per day/month
Number of masking jobs per day or per month.
Number of replication jobs per day/month
Number of replication jobs per day or per month.
Number of rows processed by PowerCenter jobs per day/month
Number of rows processed by PowerCenter jobs per day or per month.
Number of rows processed by mapping jobs per day/month
Number of rows processed by mapping jobs per day or per month.*
Number of rows processed by masking jobs per day/month
Number of rows processed by masking jobs per day or per month.
Number of rows processed by replication jobs per day/month
Number of rows processed by replication jobs per day or per month.
Number of rows processed by synchronization jobs per day/month
Number of rows processed by synchronization jobs per day or per month.
Number of state sync jobs per day
Number of state synchronization jobs per day.
State synchronization jobs include the fetchState and loadState jobs that you run through the REST API.
Number of sub-organizations
Number of sub-organizations. If you delete any sub-organizations, this meter includes the deleted sub-organizations.
Number of synchronization jobs per day/month
Number of synchronization jobs per day or per month.
Number of user-management create requests
Number of user management creation requests.
User management creation requests include requests to create users, user groups, and custom roles.
Serverless CDI Compute Hours
Deprecated. Serverless compute units measured in hours for mappings outside of advanced mode.
Serverless CDI-E Compute Hours
Deprecated. Serverless compute units measured in hours for mappings in advanced mode.
Total Serverless units used
Deprecated. Total number of serverless compute units used to run tasks.
Total compute hours used by elastic cluster nodes
Deprecated. This meter has been replaced with the Advanced Data Integration meter.
Total number of PowerCenter jobs
Total number of PowerCenter jobs.
Total number of agents
Total number of Secure Agents, including agents that are stopped. Does not include the Informatica Cloud Hosted Agent.
Total number of connections
Total number of connections.
Total number of folders
Total number of folders.
Total number of mapping jobs
Total number of mapping jobs.*
Total number of masking jobs
Total number of masking jobs.
Total number of projects
Total number of projects.
Total number of replication jobs
Total number of replication jobs.
Total number of rows processed by PowerCenter jobs
Total number of rows processed by PowerCenter jobs.
Total number of rows processed by mapping jobs
Total number of rows processed by mapping jobs.*
Total number of rows processed by masking jobs
Total number of rows processed by masking jobs.
Total number of rows processed by replication jobs
Total number of rows processed by replication jobs.
Total number of rows processed by synchronization jobs
Total number of rows processed by synchronization jobs.
Total number of synchronization jobs
Total number of synchronization jobs.
* If your organization uses Data Accelerator for Azure, this meter includes Azure data sync jobs because each Azure data sync job runs an underlying mapping.
Guidelines for Data Quality and Data Profiling assets
If you run a mapping outside of advanced mode in which a transformation reads a data quality asset, Informatica records transactions for the mapping in the Data Quality meter. If you run a mapping in advanced mode in which a transformation reads a data quality asset, Informatica records transactions for the mapping in the Data Quality Elastic meter.
If you run a profile on the Data Integration Server, Informatica records transactions for the profile in the Data Quality meter. If you run a profile on an advanced cluster, Informatica records transactions for the profile in the Data Quality Elastic meter.
You can preview the output data on a transformation in a mapping. If you preview the data on a transformation that reads a data quality asset, Informatica calculates the cost in the following ways:
•If the mapping that contains the transformation runs outside of advanced mode, it consumes Data Quality compute hours.
•If the mapping that contains the transformation runs in advanced mode, it consumes Data Quality Elastic compute hours.
Metering serverless compute units
When you view the total serverless compute units used, the meter is based on the number of serverless compute units that your organization uses to run tasks.
When the serverless runtime environment runs a task, the environment creates a virtual machine with resources based on the number of compute units that the task requests.
The minimum task duration is two minutes. If the task completes in less than two minutes, the serverless runtime environment consumes two minutes of compute units. After two minutes, compute units are consumed by the second.
If you cancel the job, the number of consumed compute units is the greater of the following values:
•The time that the job was running before it was canceled
•Two minutes
Guidelines for advanced clusters
To run a mapping in advanced mode, the serverless runtime environment creates an advanced cluster that contains one worker node with resources based on the number of serverless compute units that the task requests. If you run another task, the environment reuses idle worker nodes or adds worker nodes to the cluster to reserve additional resources.
Metering begins when the task starts running and ends when the task is complete. Metering doesn't include the time to compile the job or the time to start the cluster.
Metering doesn't take effect if the job fails before the cluster has been created, such as when the job fails to compile, the cluster fails to start, or you cancel the job before the cluster starts.
Viewing usage details
You can view detailed metering statistics. To view the detailed statistics, in the dashboard view of the Metering page, click Detail Chart for the relevant graph.
Detailed metering statistics are available for the following meters:
•Application Integration
•Application Integration with Advanced Serverless
•Catalog Records
•CDI-E Compute Hours
•Serverless CDI-E Compute Hours
•Serverless CDI Compute Hours
•Data Quality
•Data Quality Elastic
•Data Quality with Advanced Serverless
•Data Quality Elastic with Advanced Serverless
•Governance Records
•Mass Ingestion Applications
•Mass Ingestion Applications - Change Data Capture
•Mass Ingestion Databases
•Mass Ingestion Databases - Change Data Capture
•Mass Ingestion Files
•Mass Ingestion Streaming
•PC2CDI Modernization Service Assessment
•PC2CDI Modernization Service Conversion
The following image shows an example of the details page that shows the total usage for each runtime environment in the last 90 days:
You can customize the view in the following ways:
•If your organization has sub-organizations, you can view usage details for the parent organization or for a sub-organization. You cannot view usage details for a deleted sub-organization.
•You can change the grouping. For example, you can group by runtime environment to see total usage for each runtime environment or you can view the full table to see usage by date.
•You can change the date range that defines the reporting period, such the current month, last month, last 90 days, or last 6 or 13 months.
Metering usage reports
If your organization uses Application Integration, the Mass Ingestion service, advanced clusters, Cloud Data Integration for PowerCenter (CDI-PC) to modernize PowerCenter assets, or a serverless runtime environment, you can download a metering usage report.
A metering usage report contains the following information:
•For Application Integration, the report contains execution details of processes, app connections, and OData APIs. For an Application Integration advanced serverless runtime environment, the report contains execution details of processes and guides.
•For Mass Ingestion Applications and Mass Ingestion Databases, the report content depends on the load type of the ingestion job. For jobs that perform initial loads, the report contains the volume of data ingested in GBs. For jobs that perform incremental loads, the report contains the number of records, or rows, processed. For jobs that perform combined initial and incremental loads, both reports are available.
•For Mass Ingestion Files, the report contains details about the volume of data ingested by file ingestion tasks.
•For Mass Ingestion Streaming, the report contains details about the volume of data ingested by streaming ingestion jobs.
•For advanced clusters, the report contains details about the compute hours for cluster nodes.
•For Cloud Data Integration for PowerCenter (CDI-PC), the report contains details such as the date and time when assessment or conversion jobs were run, organization ID, job details, and the number of objects processed during assessment or conversion.
•For a serverless runtime environment, the report contains details about the number of serverless compute units that were requested and consumed to run tasks.
If your organization does not use Mass Ingestion Applications, Mass Ingestion Databases, Mass Ingestion Files, Mass Ingestion Streaming, advanced clusters, or a serverless runtime environment, no metering usage reports are available.
Downloading a metering usage report from Metrics Summary
Download a metering usage report from the Metrics Summary view of the Metering page.
1In Administrator, select Metering.
2If you see the dashboard view, click All Meters in the Metrics Summary This Month area to open the License Metrics view.
3Click Export to File and select Metering Usage Details.
Note: If all listed services use meters based on consumption, a warning message appears and you cannot download a metering usage report from License Metrics view.
4Select the service or product feature and the date range that you want to view, and then click Export.
Downloading a metering usage report from Detail Chart
Download a metering usage report from the Detail Chart view of the Metering page.
1In Administrator, select Metering.
2Click Detail Chart for the metering usage report you want to download.
3Select the organization and the date range that you want to view.
