Detailed AppPoints Consumption Reports for SaaS Environment

The MAS Administration License Consumption page displays Entitled Capacity and Peak Usage AppPoints with trending over time. However, it doesn't provide details on license consumption.

I reached out to IBM technical staff and there was no current solution that meets our needs. Specifically we were told that the information is only available through OpenShift which we don't have access to as SaaS customers.

Here are the details that were provided:

· Using OpenShift Audit Logs:

• Audit Logs: OpenShift generates audit logs for various activities, including user logins. By analyzing these logs, you can determine how many users are currently logged in. You can use tools like oc logs to access and filter audit logs.

· Using OpenShift OAuth Server:

• OAuth Tokens: OpenShift uses OAuth tokens for user authentication. By querying the OAuth server, you can get information about active sessions and tokens, which can indicate the number of logged-in users.

· Using OpenShift Console:

• Web Console: The OpenShift web console provides some information about active users and sessions, though it might not give a direct count of currently logged-in users. This information can be found under the "Monitoring" section.

So, we'd like a License Consumption report in the MAS application with a date range filter to list AppPoints consumption in detail. It should contain the following details over the specified date range:

1. Features that consume AppPoints by being enabled in our environment |
   Ex: Spatial being enabled consumes 20 AppPoints

2. Authorized Users consuming AppPoints via their Application and Administration entitlements.
   Ex: An admin user account may show up as consuming 3 AppPoints through Base Application Entitlement, and 10 AppPoints through Base Administration entitlement.

3. Concurrent Users that have logged in during the date range filter along with their entitlements consumed at the time of their login.

4. If MAS charges AppPoints for Users that we haven't configured properly, then include these cases.

5. If MAS charges AppPoints for different instances (ex: Dev), then have a column in the report listing the environment.

6. For each user, have a column with session start and session end