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

Refactor naming of fields and license type names used in InfluxDB to better ones #1084

Closed
mountaindude opened this issue Apr 12, 2024 · 0 comments · Fixed by #1083
Closed

Comments

@mountaindude
Copy link
Collaborator

The naming convention used when storing license information in InfluxDB didn't turn out to be ideal.
It should be updated to become more consistent with existing naming convention for InfluxDB.

License type names

Currently (11.2.0) the following names are used for the various license types tracked by Butler and stored in InfluxDB:

  • analyzer_access
  • analyzer_time_access
  • professional_access
  • login_access
  • user_access
  • tokens_available

Change to

  • analyzer
  • analyzer_capacity
  • professional
  • token_login
  • token_user
  • tokens_available

Naming of fields in InfluxDB

analyzer_capacity license type

Current field names:

  • allocatedMinutes
  • unavailableMinutes
  • usedMinutes

New field names:

  • allocated_minutes
  • unavailable_minutes
  • used_minutes

token_login license type

Current field names:

  • allocatedTokens
  • tokenCost
  • unavailableTokens
  • usedTokens

New field names:

  • allocated_tokens
  • token_cost
  • unavailable_tokens
  • used_tokens

token_user license type

Current field names:

  • allocatedTokens
  • quarantinedTokens
  • tokenCost
  • userTokens

New field names:

  • allocated_tokens
  • quarantined_tokens
  • token_cost
  • used_tokens

tokens_available license type

This is high level token information for the Qlik Sense environment as a whole.

Current field names:

  • availableTokens
  • totalTokens

New field names:

  • available_tokens
  • total_tokens
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant