简体   繁体   English

您最终为 Container Insights for EKS 为短期 Pod 创建的每个指标支付了多少费用?

[英]How much do you end up paying for each metric created by Container Insights for EKS for short lived pods?

I just enabled Container Insights in my EKS cluster following the Amazon's Quick Start Setup for Conainer Insights on Amazon EKS .我刚刚在我的 EKS 集群中启用了 Container Insights,遵循 Amazon 的Amazon EKS 上的 Conainer Insights 快速启动设置

I see that the number of metrics is quickly increasing, CloudWatch > Metrics > Custom Namespaces > ContainerInsights is already 1279 metrics with the majority of them under ClusterName, Namespace, Podname (979 metrics)我看到指标的数量在快速增加,CloudWatch > Metrics > Custom Namespaces > ContainerInsights 已经有 1279 个指标,其中大部分在 ClusterName、Namespace、Podname 下(979 个指标)

Under ContainerInsights > ClusterName, Namespace, PodName is creating 4-5 metrics for each new pod and the number of pods steadily increase since we have Airflow creating new short-lived pods all the time.在 ContainerInsights > ClusterName、Namespace 下,PodName 为每个新 pod 创建 4-5 个指标,并且 pod 的数量稳步增加,因为我们一直有 Airflow 个创建新的短期pod。

Since CloudWatch Pricing indicates that we pay 0.30$ per custom metric/month, does that means that I will get billed ~1000x0.30 = 300$?由于CloudWatch 定价表明我们每月为每个自定义指标支付 0.30 美元,这是否意味着我将收到约 1000x0.30 = 300 美元的账单? The pricing page also indicates that All custom metrics charges are prorated by the hour and metered only when you send metrics to CloudWatch .定价页面还表明所有自定义指标费用按小时按比例分配,并且仅在您将指标发送到 CloudWatch 时才计费 Since almost all the pods are short-lived (less than an hour), does that mean that I will get billed only ~1000x(0.30/(30days * 24hours)) = ~1000*(0.30/720) = 0.41$?由于几乎所有的 pod 都是短暂的(不到一个小时),这是否意味着我只会被计费 ~1000x(0.30/(30days * 24hours)) = ~1000*(0.30/720) = 0.41$?

According to Example 8 - Container Insights for Amazon EKS and Kube.netes (k8s) on the (CloudWatch Pricing page]( https://aws.amazon.com/cloudwatch/pricing/ ) up to 9 metrics will be sent per pod. In there is even clear that the metrics cost is prorated on hourly basis.根据(CloudWatch 定价页面]( https://aws.amazon.com/cloudwatch/pricing/ ) 上的示例 8 - Amazon EKS 和 Kube.netes (k8s) 的容器洞察,每个 pod 将发送最多 9 个指标。甚至很明显,指标成本是按小时按比例分配的。

I guess the best way to think about is asking yourself how many average running container you'll have during the 30 day period and use that to calculate the cost我想最好的思考方式是问问自己在 30 天内平均运行的容器数量,并用它来计算成本

(n_average_running_pods x 9 x 0.30$USD)

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 如何防止 Apache Airflow 启动的短暂 kube.netes pod 中的 CloudWatch Container Insights 指标? - How to prevent CloudWatch Container Insights metrics from short lived kubernetes pods started by Apache Airflow? 在 Amazon eks 中 - 如何查看 eks fargate 节点创建之前的日志以及 pod 启动时的日志 - In amazon eks - how to view logs which are prior to eks fargate node creation and logs while pods is starting up 在 AWS EKS 中自动扩展 POD - Autoscaling of PODs in AWS EKS 如何允许从特定 AWS EKS pod 连接到 AWS RDS? - How to allow connection from specific AWS EKS pods to AWS RDS? 如何让 kubectl 登录到 AWS EKS 集群? - How do you get kubectl to log in to an AWS EKS cluster? EKS Pod 被无故终止 - EKS Pods being terminated for no reason 如何使用 AWS 控制台/GUI 对已创建的 ECS Fargate 启用容器洞察 - How to enable container insights on already created ECS Fargate using AWS Console / GUI 您将如何升级 terraform eks 模块? - How would you upgrade the terraform eks module? EKS 集群 pod 无法连接到 inte.net - EKS cluster pods unable to connect to internet 如何使用 boto3 (python sdk) 获取 lambda 的指标日志洞察 - How to get metric log insights for lambdas using boto3 (python sdk)
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM