TAG004: unknown-history-provider
historyProvider is not configured on the gateway
| Code | TAG004 |
| Name | unknown-history-provider |
| Category | Tags and gateway (TAG) |
| Default severity | warning |
| Enabled by default | yes |
| Fix available | no |
| ign-lint equivalent | none |
What it does
Section titled “What it does”Checks the historyProvider of every tag with history enabled against the
historian providers and database connections (which serve as SQL
historians) configured in the gateway collections of the workspace. Names
are compared case-insensitively. When the workspace configures no
historian provider at all, nothing is reported.
Why is this bad?
Section titled “Why is this bad?”Tag history for a provider that does not exist is never stored: trends and reports silently have no data for the tag.
Values with UDT parameter placeholders ({Historian}) are not checked.
Example
Section titled “Example”{"name": "Speed", "historyEnabled": true, "historyProvider": "Core Historain"}Use instead:
{"name": "Speed", "historyEnabled": true, "historyProvider": "Core Historian"}Generated from the rule metadata by iglint generate-docs; iglint rule TAG004 prints the same page in the terminal. Source: docs/rules/TAG004.md.