Skip to content

feat: integrate Gemini CLI with Docker MCP for natural language observability#24134

Open
falconcr wants to merge 5 commits intodocker:mainfrom
falconcr:main
Open

feat: integrate Gemini CLI with Docker MCP for natural language observability#24134
falconcr wants to merge 5 commits intodocker:mainfrom
falconcr:main

Conversation

@falconcr
Copy link
Contributor

Description

This PR implements a natural language interface for observability by connecting the Gemini CLI to Grafana/Loki using the Docker MCP Toolkit.

The implementation allows DevOps engineers to query infrastructure logs and metrics using plain English. The workflow follows a three-step automated sequence:

Datasource Discovery: The system automatically identifies available telemetry backends (e.g., Loki) using the list_datasources tool.

Contextual Translation: Gemini translates natural language prompts (e.g., filtering by device_name) into technical LogQL queries autonomously.

Automated Diagnostics: The system summarizes raw logs and proactively identifies critical anomalies, such as node_filesystem_device_error, without explicit user instruction.

Reviews

Checklist

[x] Technical review

[ ] Editorial review

[ ] Product review

@netlify
Copy link

netlify bot commented Feb 11, 2026

Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit e7b4ade
🔍 Latest deploy log https://app.netlify.com/projects/docsdocker/deploys/69b9ad47c9e62f0008f770d2
😎 Deploy Preview https://deploy-preview-24134--docsdocker.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@craig-osterhout
Copy link
Contributor

/review

Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Documentation Review Summary

I've reviewed the new Grafana MCP integration guide. The content is well-structured and provides a useful tutorial for DevOps engineers. However, I found several issues that should be addressed to improve clarity and completeness:

HIGH Severity Issues (3):

  • Missing explanation for security recommendations
  • Unclear description of AI behavior in logs inspection
  • Incomplete help/contact information

MEDIUM Severity Issues (5):

  • Wordy phrasing that could be more concise
  • Passive voice construction
  • Marketing metaphors instead of direct language
  • Unclear technical assumptions about Kubernetes
  • Promotional tone in closing section

All issues are detailed in inline comments below.

Copy link
Contributor

@dvdksn dvdksn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for this @falconcr

For now, just a heads-up that we're about to release some changes to MCP Toolkit which affects the UX in a way that would impact some of the steps in this guide. We're introducing an abstraction layer for managing server<>client configurations, called profiles.

The guide as such will still be useful. But I think we should wait with releasing this until profiles have been released, to avoid the double work of releasing this now and then updating it in a week or two when profiles are released.

@falconcr
Copy link
Contributor Author

Thank you for this @falconcr

For now, just a heads-up that we're about to release some changes to MCP Toolkit which affects the UX in a way that would impact some of the steps in this guide. We're introducing an abstraction layer for managing server<>client configurations, called profiles.

The guide as such will still be useful. But I think we should wait with releasing this until profiles have been released, to avoid the double work of releasing this now and then updating it in a week or two when profiles are released.

Hello @dvdksn , i just applied the feedback provided. Let me know if you have more comments or when the new release is done in order to update the repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants