You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 23, 2023. It is now read-only.
Issue: if tsdb-gw is configured with v2 = true, v2-org = true and org-id=0 metrictank ignores corresponding v2 (i.e. metricPoint) messages from Kafka, counting them as unknown.
Workaround:
or disable mdm v2: set v2 = false
or change org-id to any positive value, e.g. set org-id=1.
The text was updated successfully, but these errors were encountered:
I think the problem might be that we decided in some parts to reject orgid=0 (because if that data comes in, we don't know the difference between set to 0 or unspecified) while in other places allowing it, or even defaulting to it.
see #260
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Not sure is it related to metrictank or tsdb-gw.
Setup: tsdb-gw v0.9.0-g72ce022 -> Kafka (0.10.x, 0.11.x, 1.1) -> metrictank 0.9.0-304-g095aaa4
Issue: if tsdb-gw is configured with
v2 = true
,v2-org = true
and org-id=0 metrictank ignores corresponding v2 (i.e. metricPoint) messages from Kafka, counting them asunknown
.Workaround:
or disable mdm v2: set
v2 = false
or change org-id to any positive value, e.g. set org-id=1.
The text was updated successfully, but these errors were encountered: