[🐛 Bug]: inconsistent capitalization of “VictoriaMetrics” across documentation and code
Summary
On the documentation page for the VictoriaMetrics provider,
👉 https://docs.keephq.dev/providers/documentation/victoriametrics-provider,
the product name appears everywhere as “Victoriametrics” (with a lowercase m).
At the same time, on the VictoriaLogs page
👉 https://docs.keephq.dev/providers/documentation/victorialogs-provider,
the name VictoriaLogs is written correctly — with Logs capitalized.
The correct and official spelling is VictoriaMetrics (capital M).
🧩 Steps to reproduce
- Open https://docs.keephq.dev/providers/documentation/victoriametrics-provider
- Observe that the name “Victoriametrics” is written with lowercase m throughout the text
- Compare with https://docs.keephq.dev/providers/documentation/victorialogs-provider — where capitalization is correct
💡 Expected behavior
All references to the product should use the correct capitalization:
VictoriaMetrics
This includes:
- Documentation titles and headings
- Provider descriptions
- Source code identifiers (if applicable, e.g. provider display names)
✅ Proposed fix
- Update all documentation pages and metadata files to use “VictoriaMetrics” (capital M).
- Verify in the codebase (provider definitions, UI labels, etc.) that naming consistency is preserved.
- Optionally, add a simple linting rule or doc-check to avoid inconsistent capitalization in the future.
🧠 Rationale
Consistent use of proper product names improves:
- Professional appearance of documentation
- Brand accuracy for external integrations
- Searchability within the docs and UI
Labels: type:bug area:documentation priority:low
You're right—there's inconsistent capitalization of "VictoriaMetrics" in both the documentation and the codebase. The provider docs and workflow examples use "Victoriametrics" (lowercase "m") throughout, while the correct spelling is "VictoriaMetrics" (capital "M") docs. The same issue appears in the provider implementation, where the main class and identifiers use the lowercase "m" provider code.
There's an open issue tracking this naming consistency problem: #4730. No linting or automation currently enforces capitalization for provider names, so manual updates are needed in docs, code, and metadata. For future consistency, adding a simple doc-check or linting rule to flag incorrect product name capitalization would help prevent regressions.
Let me know if you want details on specific files or examples to update!
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other