Settings and activity
15 results found
-
18 votes
Nikola supported this idea ·
-
2 votes
-
3 votes
An error occurred while saving the comment -
12 votes
-
7 votes
-
3 votesFuture Consideration · 0 comments · DoiT Cloud Intelligence » Attributions & Attribution Groups · Admin →
-
7 votes
-
8 votes
-
3 votes
We have already build a way to identify such monthly cost spikes and suppress them. We already support a range of services there already and any other new service can be requested to this list via our support ticket. Here is the information about existing capability https://help.doit.com/docs/governance/cloud-anomalies#spikes-at-the-beginning-of-the-month
-
6 votes
-
10 votes
-
11 votes
An error occurred while saving the comment With the newly introduced DataHub, it would be great if we could provide connectors for easy ingestion of cloud sustainability data:
- AWS: https://aws.amazon.com/blogs/aws-cloud-financial-management/increased-visibility-of-your-carbon-emissions-data-with-aws-customer-carbon-footprint-tool/
- GCP: https://cloud.google.com/carbon-footprint/docs/exportThis functionality would allow allocation and visualization of sustainability data behind a single pane of glass within DoiT Navigator.
(This idea supports the implementation of https://uservoice.doit.com/forums/957092-doit-cloud-navigator/suggestions/48342290-support-cloud-carbon-footprint-reporting.)
-
4 votes
-
9 votes
-
4 votes
One addition that could even potentially simplify the implementation. Instead of trying to implicitly deduct if the customer found the anomaly too low for the threshold they have in mind for what an anomaly means, we could also add an option in the anomaly acknowledgment that says something along "The spike is too low to be considered an anomaly". This would be the exact use case for applying anomaly thresholds.