Kubecost sensor releases

Improvements

The sensor now generates events to detect Kubecost connectivity issues.

Fixes

Previously, when a longer time range was selected in the Date and time picker in the Instana UI, the Cost By Namespace and Cost By Deployment table on the Cost tab on the Kubernetes cluster dashboard did not display the trend value. This issue is fixed now.

Improvements

The Kubecost sensor now supports both Kubecost (foundations) and Enterprise (self-hosted or cloud) license. Also, the sensor now dynamically fetches cost metrics for all active clusters from Kubecost even if the cluster names are not specified in the Instana agent configuration file. Previously, specifying one or more Kubecost cluster names was required. For more information, see Integrating with IBM Kubecost.

If a list of one or more clusters is specified in the agent configuration file, Instana fetches cost metrics only for those clusters.

Features

This release adds the following features:

• The sensor can now establish authentication-based connection to Kubecost REST API.
• The sensor now displays Kubecost license tier in the Instana UI.

Improvements

This release improves logging for better debugging.

Fixes

This release fixes the following issues:

• Null response to allocation API call.
• 414 Request-URI Too Large error that occurred when trends API is called.

Features

• The Kubecost sensor 1.0.5 now generates events for V-CPU exceeded threshold.
• The sensor also displays the deployment cost, estimated monthly savings, total cluster cost, and workload efficiency.

Fixes

This release fixes the spikes in Cost by namespace view.

Improvements

The Kubecost sensor now accepts both the demo.kubecost.xyz and http://kubecost.demo.xyz URL formats.

Fixes

This release fixes the following issues:

• Previously, if currency identifier was not configured during Kubecost deployment, the Instana UI did not display the default cost identifier. This issue is now fixed, and you can see the default cost identifier in the UI.
• Previously, the cost calculations were inaccurate due to the use of partial time window-based metrics. This issue is now fixed by calculating the cost without these metrics.

Features

Kubecost is now available as a separate filter under Analytics > Infrastructure > Entity type in the Instana UI. For more information about Kubecost, see Integrating with IBM Kubecost.

Improvements

The sensor now employs threadpools to improve the efficiency of metrics collection.