Semantic Conventions for licencing #1129
Labels
area:new
enhancement
New feature or request
experts needed
This issue or pull request is outside an area where general approvers feel they can approve
triage:needs-triage
Area(s)
area:new
Is your change request related to a problem? Please describe.
In my workplace we deploy a lot of on-premise software managed via time based licences and currently we are simply writing to the log when it is expired or close to expiring with the hope a user sees in the log that it is close to expiring/has expired. By moving to a convention driven attribute approach we would be able to take these structured machine events and visualise them more efficently I see this also playing a role in applications such as firewalls, switches etc which might require subscriptions for functionality to corrrecly operate
Describe the solution you'd like
I would like for their to be an attribute group defined which can be used to describe the licencing state of the application/library so that i can easily see find events when my applications are getting close to renewal etc.
licencing.status
-> strongly typed string field of ie licenced, unlicensed, expiredlicencing.type
-> strongly typed string field of types ie subscription, perpetual, triallicencing.expiry
-> the date when the subscriptionDescribe alternatives you've considered
Implement my own conventions
Additional context
No response
The text was updated successfully, but these errors were encountered: