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

Create observability-platform-cost-estimate #637

Merged
merged 2 commits into from
Oct 23, 2024

Conversation

Rotfuks
Copy link
Contributor

@Rotfuks Rotfuks commented Oct 22, 2024

Introduce new dashboard for estimating observability platform costs.

This PR

  • adds/changes/removes etc
  • screenshots before:
  • screenshots after:

Checklist

  • Update changelog in CHANGELOG.md in an end-user friendly language.

Introduce new dashboard for estimating observability platform costs.
@Rotfuks Rotfuks requested a review from a team as a code owner October 22, 2024 15:03
@QuantumEnigmaa
Copy link
Contributor

Could you show screenshots from your dashboard pls ? 🙏

@Rotfuks
Copy link
Contributor Author

Rotfuks commented Oct 22, 2024

sure sure, here's the dashboard @QuantumEnigmaa 

@QuantumEnigmaa
Copy link
Contributor

I have a few remarks & questions :

  • On what time period are the increase and decrease displayed ? Is it the interval selected on default
  • I guess that you're displaying the average number of nodes to ease the calculation of cost based on how much does a node cost (from its machine type) but that might not be straight forward to understand. Could you maybe add some text below to explain why is this metric displayed ?
  • Could you add a "CPU cores" unit for the CPU Usage graph pls ?

…/private/observability-platform-cost-estimate

Co-authored-by: Hervé Nicol <[email protected]>
@Rotfuks
Copy link
Contributor Author

Rotfuks commented Oct 23, 2024

@QuantumEnigmaa 

  • On what time period are the increase and decrease displayed ? Is it the interval selected on default

Yep, it's just the default interval, I didn't set anything specific. But it makes sense compared to the displayed graph

  • I guess that you're displaying the average number of nodes to ease the calculation of cost based on how much does a node cost (from its machine type) but that might not be straight forward to understand. Could you maybe add some text below to explain why is this metric displayed ?

The average number of nodes is just generally all numbers of nodes in the cluster - that's important because some competitors like DataDog and Dynatrace calculate their price based on the amount of nodes monitored. So it's quite straight forward I think :D That's why the second section is just a collection of other metrics that are useful for calculations, but our own cost calculation just needs the first 4 visualisations from the first section

  • Could you add a "CPU cores" unit for the CPU Usage graph pls ?

It's in the description, that the number is cpu cores - is that enough for you?

@QuantumEnigmaa
Copy link
Contributor

QuantumEnigmaa commented Oct 23, 2024

It's in the description, that the number is cpu cores - is that enough for you?

Yeah I guess it's fine, I'm just nitpicking here :)

some competitors like DataDog and Dynatrace calculate their price based on the amount of nodes monitored

Ok makes sense then.

@Rotfuks Rotfuks merged commit b3fdf08 into main Oct 23, 2024
4 checks passed
@Rotfuks Rotfuks deleted the observability-platform-cost-dashboard branch October 23, 2024 12:52
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

Successfully merging this pull request may close these issues.

3 participants