Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Axis labelling, 2nd axis #3

Closed
davebarr opened this issue Nov 15, 2010 · 1 comment
Closed

Axis labelling, 2nd axis #3

davebarr opened this issue Nov 15, 2010 · 1 comment

Comments

@davebarr
Copy link
Contributor

The current graphing stuff makes it hard to distinguish when a given plot is using the first or second Y axis if you're just looking at the resulting image.

To make this easier to understand, the plan is to let you specify a text label to apply to each axis so that based on the metric name in the legend you can figure out which axis is the appropriate one.
@tsuna
Copy link
Member

tsuna commented Jan 23, 2011

Implemented as of StumbleUponArchive/opentsdb@d869c5c

@jarajapu jarajapu mentioned this issue Feb 21, 2014
Closed
@githubu1 githubu1 mentioned this issue Mar 31, 2016
Open
manolama pushed a commit to manolama/opentsdb that referenced this issue Jul 13, 2016
@thatsafunnyname @manolama
Use thread safe ConcurrentHashMap. (OpenTSDB#3)
f2e7cb2 
For OpenTSDB#823
Concurrent use of a HashSet can trigger race conditions and an infinite loop(s), use the thread-safe ConcurrentHashMap to avoid this.
Making the change just for the thread stack seen looping.
manolama pushed a commit that referenced this issue Jul 13, 2016
@thatsafunnyname @manolama
Use thread safe ConcurrentHashMap. (#3)
6582775 
For #823
Concurrent use of a HashSet can trigger race conditions and an infinite loop(s), use the thread-safe ConcurrentHashMap to avoid this.
Making the change just for the thread stack seen looping.

Signed-off-by: Chris Larsen <clarsen@yahoo-inc.com>
manolama pushed a commit that referenced this issue Jul 13, 2016
@thatsafunnyname @manolama
Use thread safe ConcurrentHashMap. (#3)
d3ecb53 
For #823
Concurrent use of a HashSet can trigger race conditions and an infinite loop(s), use the thread-safe ConcurrentHashMap to avoid this.
Making the change just for the thread stack seen looping.

Signed-off-by: Chris Larsen <clarsen@yahoo-inc.com>
manolama pushed a commit that referenced this issue Jul 13, 2016
@thatsafunnyname @manolama
Use thread safe ConcurrentHashMap. (#3)
7242550 
For #823
Concurrent use of a HashSet can trigger race conditions and an infinite loop(s), use the thread-safe ConcurrentHashMap to avoid this.
Making the change just for the thread stack seen looping.

Signed-off-by: Chris Larsen <clarsen@yahoo-inc.com>
@mzw-g mzw-g mentioned this issue Oct 10, 2016
Closed
@xugirl xugirl mentioned this issue Mar 19, 2018
Open
@linweisen linweisen mentioned this issue Nov 26, 2019
Closed
@ywww ywww mentioned this issue Jul 22, 2020
Closed
oyvindwe added a commit to oyvindwe/opentsdb that referenced this issue Dec 4, 2020
@oyvindwe
Support synchronous delete (OpenTSDB#3)
32cb55d 
Support synchronous delete
@15980583357 15980583357 mentioned this issue Jan 13, 2022
Open
This issue was closed.
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tsuna @davebarr