Skip to content

feat(dashboards): Add AreaChartWidget #81962

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

Merged
merged 8 commits into from
Dec 20, 2024

Conversation

gggritso
Copy link
Member

@gggritso gggritso commented Dec 11, 2024

Adds an AreaChartWidget. Just like LineChartWidget but doesn't support as many features for now! This creates a whole bunch of code duplication that I'll resolve over time.

Closes #81836

e.g.,
Screenshot 2024-12-11 at 11 03 53 AM

@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Dec 11, 2024
Copy link

codecov bot commented Dec 11, 2024

Bundle Report

Changes will increase total bundle size by 20.61kB (0.06%) ⬆️. This is within the configured threshold ✅

Detailed changes
Bundle name Size Change
app-webpack-bundle-array-push 32.04MB 20.61kB (0.06%) ⬆️

@gggritso gggritso marked this pull request as ready for review December 11, 2024 16:54
@gggritso gggritso requested a review from a team as a code owner December 11, 2024 16:54
Copy link
Member

@narsaynorath narsaynorath left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This all looks good to me, it's clear what the area chart is doing!

I only raised a product concern about mismatching types. fwiw explore allows you to turn on an area chart and they don't stack, which makes mismatched types more sensical? I think it's probably a result of moving fast and not exactly intended though. We should check if there's a valid use case for mismatched type area charts. For lines, plotting something like throughput and latency make sense, but I also think we should support multiple y-axis sometime. i.e. this is all good, it just raised some thoughts about how area charts are supposed to work

// show an error.
const firstSeries = props.timeseries[0];

// TODO: Raise error if attempting to plot series of different types or units
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not that I disagree, but line charts could conceivably plot different types so this is where some behaviour would diverge. Is this restriction intended to satisfy the "area charts show parts of a whole" detail? We'll have to consider how this is handled with the widget builder because I don't think this restriction exists there yet.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤔 is it possible in the Widget Builder to query mismatched data? If yes, how does that work, what does the Y Axis do? If I plot, say, duration and error rate

@gggritso gggritso merged commit 19ba6e7 into master Dec 20, 2024
44 checks passed
@gggritso gggritso deleted the feat/dashboards/area-chart-widget branch December 20, 2024 17:51
andrewshie-sentry pushed a commit that referenced this pull request Jan 2, 2025
Adds an `AreaChartWidget`. Just like `LineChartWidget` but doesn't
support as many features for now! This creates a whole bunch of code
duplication that I'll resolve over time.

Closes #81836
@github-actions github-actions bot locked and limited conversation to collaborators Jan 5, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Scope: Frontend Automatically applied to PRs that change frontend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Implement AreaChartWidget up to Insights Landing Pages spec
2 participants