@NishantK5584

You can’t plug Pega “directly” into Flexera, so the usual approach is to send Pega’s runtime and usage data to something Flexera can read and then build views there. First, decide which metrics you need in Flexera (node count, JVM usage, active users, request volume, application list, environments, etc.). Next, enable and standardize logging/metrics from Pega: use PDC and platform logs (PEGA, ALERT, GC, health checks) plus any custom log categories you need for license/usage, then export these into a central location (S3, Azure Blob, or a log forwarder). On the Flexera side, configure a data source or connector that can pull from that repository or from your existing observability layer (like Splunk, Dynatrace, AppDynamics, or Prometheus) which already collects Pega metrics. Map the Pega fields (app name, ruleset, environment, CPU/memory, user counts, transaction counts) to Flexera objects so dashboards and cost/compliance views are meaningful. Finally, validate with one non-prod environment, refine what you track (drop noisy metrics, keep license-relevant and capacity metrics), and then roll it out to all environments with a simple runbook so ops and licensing teams know how to maintain it.