What's new from Grafana Labs

Using Trace to profiles, you can use Grafana’s ability to correlate different signals by adding the functionality to link between traces and profiles.

Trace to profiles lets you link your Grafana Pyroscope data source to tracing data. When configured, this connection lets you run queries from a trace span into the profile data.

Throughout Kubernetes Monitoring, hover to reveal the copy icon. You can click to copy any text so that you can:

• Use it in your own query.
• Paste it in the command line.
• Send it to others.

When using the Grafana Kubernetes Monitoring Helm chart to configure with the configuration wizard, you can select IBM Cloud as a platform.

The improved navigation menu gives you a better overview by showing all levels of navigation items in a more compact design. We also implemented a better dock and imprved scrolling behavior. Furthermore, we improved the structure of the nav menu and added several new items.

Table view was created to help facilitate ease of use in a point and click UI, as opposed to data source specific query language formatting options, like loki’s line_format.

Tables can be configured and shared with team members via explore URLs or by adding the table to a dashboard panel.

Plugins can now add custom actions into Grafana’s command palette. Actions can link directly to a plugin page, or open a modal to allow users to interact with a plugin without losing their current page.

In Grafana Cloud you can use the new ‘Run investigation’ action to start a Sift investigation from anywhere in Grafana. Keep an eye out for new actions appearing in your command palette in the near future!

Grafana AWS observability introduces monitoring for your EC2 instances, all within an embedded experience, and without the need for managing or configuring local agents or building dashboards.

From the list of scrape jobs, you can navigate to your list of EC2 instances shown on the Overview tab, and drill into instance details.

Cost monitoring and investigation and troubleshooting of CPU and memory usage are now easier for both Clusters and Nodes. Go to the optimization panels for the Cluster and Node detail pages to view the CPU and memory utilization, as well as cost information.

These graphs show a history based on the time range you select.

On any panel of the Cost page in Kubernetes Monitoring, click the Explore button.

The Metrics status tab, which shows the configuration status of Kubernetes Monitoring components, is updated for better usability and quicker comprehension.

When configuring Kubernetes Monitoring with the streamlined configuration wizard that uses Grafana Kubernetes Helm Chart, you can select the platform you are using.

CPU and memory usage graphs and details, along with associated costs, are available on these pages in Kubernetes Monitoring:

• Namespace details page
• Workload detail page

(Release 1.5.0)

View the details of any container, pod, workload & namespace with these improved pages, which include CPU and memory utilization graphs and cost details.

The container page also shows adjacent restart and termination panels so you can visually correlate more quickly the restart and termination events, along with the reason for termination.

To aid in understanding historical data, a time range selector is available on every page of Kubernetes Monitoring where this function is appropriate. This selector is also available on the Workloads detail page, for detecting outlier CPU usage in the Pods. (Release 1.4.0)

Sometimes profile stacks contain lots of levels with similar repeating items, for example long stacks of framework code that usually isn’t of interest but takes up a lot of visual real estate. With this feature, instead of rendering all of the similar items we render only one and allow to expand those collapsed items on demand.

To try it out, enable the ‘traceToProfiles’ feature toggle. To enable it in your Grafana Cloud stack, contact Grafana Support.