influxdata / influxdata/ui

Ability to set Multiple Y scales in the UI for diffrent data

Open
#6,891 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement team/ui
Dominant language
TypeScript
Stars
117
Forks
51
Avg merge
2d 15h
Merged PRs (30d)
4

Description

**Proposal:**
The ability to have 2 different Y axis scales. I have 2 sets of data for 1 tag. These pieces of data are closely related and I want to map out their action on the same graph. The problem is when I am looking at it through the UI, The values are so far apart that they look like a straight line. So I want to be able to have 2 Y axis scales for the different data sets.

**Current behavior:**
Only able to have one Y scale for data that has different scaling factors.

**Desired behavior:**
The image is an example of what I am envisioning. To be able to set the scales for multiple Y axis's or having influxdb ui decide what the scale should be for each type of data. It would be nice to be able to create at least 2 different y axis, if not more in the UI
![image](https://github.com/influxdata/ui/assets/8990377/0eb3d248-bb2d-46f0-adb7-852b088dc70d)
![multiaxes](https://github.com/influxdata/ui/assets/8990377/ba727e24-e6ca-4d14-8869-79f090ed6d8d)

**Alternatives considered:**
Mapping the data on my own outside of the UI

**Use case:**
Why is this important (helps with prioritizing requests)?
This is important as data that have different value scales(like a scale of 1-100 for one type of data and other scale is in the Millions) that are closely related.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named in the issue. Start by tracing the UI graph configuration and rendering path for the current single Y scale, then determine how related data sets are represented. Done means the UI supports at least two independently scaled Y axes for closely related data.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
data-visualization, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.