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

Tech stack decision - Tremor or NewRelic Widgets #3

Closed
Tracked by #1
Amzani opened this issue Feb 9, 2024 · 1 comment
Closed
Tracked by #1

Tech stack decision - Tremor or NewRelic Widgets #3

Amzani opened this issue Feb 9, 2024 · 1 comment

Comments

@Amzani
Copy link
Owner

Amzani commented Feb 9, 2024

Related to #1

@Amzani Amzani mentioned this issue Feb 9, 2024
3 tasks
@Amzani
Copy link
Owner Author

Amzani commented Feb 15, 2024

/progress 100

Decided to go for Tremor library instead of default NewRelic widgets:

  • We will have more flexibility on how to show and compute insights (e.g Time to First API design is impossible to show in NR dashboard Metrics readiness #2 (comment))
  • As a visitor, you need a NewRelic account to see NewRelic dashboards
  • Future opportunity to centralize all our Insights in one place

Rabbit holes:

  • To prevent being Rate Limited we can cache NR API Requests

@Amzani Amzani closed this as completed Feb 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant