Skip to content

Distinguish floating/node-locked usage and track used features by version #211

@maneaGauthier

Description

@maneaGauthier

Proposal

Hello team,

First of all, thank you for maintaining this great exporter! It works perfectly, but I am currently facing some visibility limitations when dealing with complex license pools. I would like to suggest two feature enhancements that would be incredibly valuable.

  1. Distinguish between floating and node-locked/named licenses (High Priority)

Currently, it is quite difficult to separate the usage of floating licenses from node-locked/named (uncounted) licenses in the metrics.

It would be extremely helpful to have dedicated metrics for this, such as:
-flexlm_feature_used_nodelocked
-flexlm_feature_used_floating
Alternatively, adding a type="floating|nodelocked" label to the existing flexlm_feature_used metric would be the perfect Prometheus way to handle it.
Even if only one of the two types is explicitly exported, it would be enough, as we could easily deduce the other one using basic PromQL math.

  1. Track feature usage by specific version (Secondary Priority)

In environments where multiple versions of the same feature coexist (e.g., a pool of 10 licenses for v1.0, and another pool of 10 for v2.0), the current flexlm_feature_used metric only provides a global total. If 5 licenses are currently checked out, we have no way of knowing how many belong to v1.0 and how many to v2.0.

Would it be possible to append a version label directly to the flexlm_feature_used metric? This would allow us to accurately map active usage to the corresponding specific license file/contract.
Thank you in advance for your time and for considering these additions!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions