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

Properly serve data to frontend #19

Open
6 of 7 tasks
KevinMGranger opened this issue Feb 7, 2024 · 3 comments
Open
6 of 7 tasks

Properly serve data to frontend #19

KevinMGranger opened this issue Feb 7, 2024 · 3 comments
Labels
app.kubernetes.io/name=pelorus-api kind/feature Categorizes issue or PR as related to a new feature.

Comments

@KevinMGranger
Copy link
Contributor

KevinMGranger commented Feb 7, 2024

Remaining work items:

  • overall SDP score section
  • deployment freq graph
  • deployment freq deployment list
  • all MTTR except day count (although day count is buggy)
  • all CFR except main percentage
  • remove focus / "elite" badges (goodhart's law)
  • date picker
@KevinMGranger
Copy link
Contributor Author

day count bug: the seconds are being converted to days, so it rounds down too close to zero.

We should consider code / a library to intelligently find the right unit, or allow changing it.

@KevinMGranger
Copy link
Contributor Author

The date picker properly reports a range, but the function it passes through for the URL parameter collapses it too much. We need to support passing an offset in the frontend and/or backend, depending upon how the range is already handled.

@etsauer etsauer added kind/feature Categorizes issue or PR as related to a new feature. app.kubernetes.io/name=pelorus-api labels Mar 13, 2024
@etsauer
Copy link
Collaborator

etsauer commented Mar 14, 2024

@KevinMGranger how do you feel about this as the solution? lab-monkeys/developer-intelligence-prototype#8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
app.kubernetes.io/name=pelorus-api kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

2 participants