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

OpenTSDB has a hard-coded limit of 8 tags per datapoint #1062

Closed
swsnider opened this Issue Sep 8, 2015 · 6 comments

Comments

Projects
None yet
5 participants
@swsnider
Copy link
Contributor

swsnider commented Sep 8, 2015

If you attempt to submit a datapoint with more than 8 tags, OpenTSDB will return an error.

See OpenTSDB/opentsdb#437

We should handle this like we do NaN, and avoid sending these points.

@fabxc

This comment has been minimized.

Copy link
Member

fabxc commented Sep 9, 2015

Tough one. Makes OpenTSDB pretty useless as a Prometheus remote storage in my opinion – this also gives people reasons to design their metrics around limitations of down stream components.

@beorn7

This comment has been minimized.

Copy link
Member

beorn7 commented Sep 9, 2015

Yes, known issue.

We definitely need to document that and think about a fallback mechanism once OpenTSDB support is not purely experimental.

@beorn7

This comment has been minimized.

Copy link
Member

beorn7 commented Sep 9, 2015

Fallback might not be reasonably possible. Probably just not write the affected time series out to OpenTSDB and issue warnings about it.

@brian-brazil brian-brazil added the bug label Dec 16, 2015

@fabxc

This comment has been minimized.

Copy link
Member

fabxc commented Apr 6, 2016

From recent discussion this is no longer the case: #10 (comment)

@fabxc fabxc closed this Apr 6, 2016

@grobie

This comment has been minimized.

Copy link
Member

grobie commented Apr 6, 2016

For reference, the limit is controlled by tsd.storage.max_tags and still defaults to 8.

@lock

This comment has been minimized.

Copy link

lock bot commented Mar 24, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 24, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.