fix: prometheus docs

[0xi4o]

Updated prometheus docs to reflect changes in configuration from FlowiseAI/Flowise#5562

[gemini-code-assist]

Summary of Changes

Hello @0xi4o, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a documentation discrepancy by updating the Prometheus monitoring guide to accurately reflect recent changes in the configuration of the /api/v1/metrics endpoint. The primary goal is to inform users that this endpoint now requires API key authentication and to provide clear, step-by-step instructions, including a configuration example, on how to set up Prometheus to correctly authenticate and collect metrics from Flowise.

Highlights

• Prometheus Authentication: The documentation for Prometheus monitoring has been updated to reflect that the /api/v1/metrics endpoint now requires API key authentication.
• Configuration Instructions: New instructions have been added detailing how to generate an API key, save it to a file, and configure Prometheus to use bearer token authentication for scraping metrics.
• Multilingual Documentation Update: Both the English (en/using-flowise/monitoring.md) and Spanish (esp/usar-flowise/monitoring.md) versions of the monitoring documentation have been updated with these changes.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the Prometheus monitoring documentation in both English and Spanish to reflect the new requirement for API key authentication on the metrics endpoint. The changes include adding sections on authentication setup and updating the Prometheus configuration example, which aligns the documentation with recent application changes. My review includes suggestions to improve link maintainability by using relative paths for internal documentation links instead of absolute URLs.