Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Semantic Conventions for licencing #1129

Open
thompson-tomo opened this issue Jun 6, 2024 · 0 comments
Open

Semantic Conventions for licencing #1129

thompson-tomo opened this issue Jun 6, 2024 · 0 comments
Assignees
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

Comments

@thompson-tomo
Copy link

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, expired
  • licencing.type -> strongly typed string field of types ie subscription, perpetual, trial
  • licencing.expiry -> the date when the subscription

Describe alternatives you've considered

Implement my own conventions

Additional context

No response

@thompson-tomo thompson-tomo added 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 labels Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

2 participants