Skip to content
This repository was archived by the owner on Aug 23, 2023. It is now read-only.

mdm v2 input with org-id = 0 is not working #1026

Closed
deniszh opened this issue Aug 29, 2018 · 2 comments
Closed

mdm v2 input with org-id = 0 is not working #1026

deniszh opened this issue Aug 29, 2018 · 2 comments
Labels

Comments

@deniszh
Copy link

deniszh commented Aug 29, 2018

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 as unknown.

Workaround:
or disable mdm v2: set v2 = false
or change org-id to any positive value, e.g. set org-id=1.

@Dieterbe
Copy link
Contributor

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

@stale
Copy link

stale bot commented Apr 4, 2020

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.

@stale stale bot added the stale label Apr 4, 2020
@stale stale bot closed this as completed Apr 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants