opensource/grafana
1
0
Fork 0
mirror of https://github.com/grafana/grafana.git synced 2025-08-02 15:52:29 +08:00
Code Issues Packages Projects Releases Wiki Activity
Files
grafana/docs
History
Alexander Akhmetov c54da8f955 Alerting: Make $value return the query value in case when a single datasource is used (#102301) 
What is this feature?

This PR changes the behavior of the $value and .Value variables in alerting templating to be more compatible with Prometheus templating. When a single datasource is used in the alerting rule, these variables will now return the numeric value from the query instead of the evaluation string.

Why do we need this feature?

It makes Grafana templating more compatible with Prometheus templates. In Prometheus, $value returns the numeric value of the query, but in Grafana it's the evaluation string: [ var='A' labels={instance=instance1} value=81.234 ]. This is because in Grafana multiple datasources can be used in the alert rule, and it's not always possible to get a single value.

This change makes Grafana's behavior consistent with Prometheus when a single datasource is used, and in case when multiple datasources are used in the query, it keeps the old behaviour.

Both $value and .Value are not recommended to use (documentation), and it's better to use .Values instead.
2025-03-26 10:31:38 +01:00
..
sources
Alerting: Make $value return the query value in case when a single datasource is used (#102301)
2025-03-26 10:31:38 +01:00
.gitignore
…
docs.mk
Update make docs procedure (#101497)
2025-03-07 10:38:11 +00:00
logo-horizontal-dark.png
Docs: Invert logo color for dark theme in README (#76012)
2023-11-07 09:54:12 +00:00
logo-horizontal.png
…
make-docs
Update make docs procedure (#101497)
2025-03-07 10:38:11 +00:00
Makefile
Docs: Add dashboard variables content (#101733)
2025-03-07 09:55:39 -05:00
README.md
Remove relref shortcodes (#101694)
2025-03-06 13:59:08 +01:00
variables.mk
…

README.md

Building the docs locally

When you contribute to documentation, it's a good practice to build the docs on your local machine to make sure your changes appear as you expect. This README explains the process for doing that.

To build a local version, you need to run a process in a Docker container. Grafana periodically updates the Docker image, docs-base, to update the styling of the Docs.

Requirements

  • Docker >= 2.1.0.3
  • Yarn >= 1.22.4

Build the doc site

First, make sure the Docker daemon is running on your machine. Then, follow these steps:

  1. On the command line, first change to the docs folder: cd docs.
  2. Run make docs. This launches a preview of the website with the current grafana docs at http://localhost:3002/docs/grafana/latest/ which will refresh automatically when changes are made to content in the sources directory.

If you have the grafana/website repo checked out in the same directory as the grafana repo, then you can run make docs-local-static to use local assets (such as images).

Deploy preview

When you open a PR that changes files in the docs/sources/ directory, CI builds a deploy preview. After the deploy preview has been built, the Deploy pr preview workflow comments a link to the preview URL and adds a commit status check .

Content guidelines

Generally, one can edit content in the sources directory.

The following paths are built instead from a typescript file and are auto-generated. Please do not edit these files directly. Instead, navigate to the appropriate typescript source file and edit the content there, then follow the build instructions to generate the markdown files.

Transformations

Auto-generated markdown location:

  • docs/sources/panels-visualizations/query-transform-data/transform-data/index.md

Typescript location for editing and instructions:

  • scripts/docs/generate-transformations.ts - Includes all content not specific to a transformation.
  • public/app/features/transformers/docs/content.ts - Transformation-specific content.

Only use reference style links in the content.ts file or else link text will be visible in the UI.

Contributing

Managing redirects

When moving content around or removing pages it's important that users following old links are properly redirected to the new location. We do this using the aliases feature in Hugo.

If you are moving a page, add an aliases entry in the front matter referencing the old location of the page which will redirect the old url to the new location.

If you are removing a page, add an aliases entry in the front matter of the most-applicable page referencing the location of the page being removed.

If you are copying an existing page as the basis for a new one, be sure to remove any aliases entries in the front matter in your copy to avoid conflicting redirects.

Edit the side menu

The side menu is automatically build from the file structure. Use the weight front matter parameter to order pages.

To specify different menu text from the page title, use the front matter parameter menuTitle.

Add images

Please see our help documentation on Image, diagram, and screenshot guidelines for comprehensive information.

Deploy changes to grafana.com

When a PR is merged with changes in the docs/sources directory, those changes are automatically synced by a GitHub action (.github/workflows/publish.yml) to the grafana/website repo.

  • A PR that targets the main branch syncs to the content/docs/grafana/next directory in the website repository, and publishes to https://grafana.com/docs/grafana/next/.
  • A PR targeting the latest/current release branch syncs to the content/docs/grafana/latest directory in the website repository, and publishes to https://grafana.com/docs/grafana/latest/.

Once the sync is complete, the website will automatically publish to production - no further action is needed.