Update template_variables.md #32390
Open
Update template_variables.md #32390
+14
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Preview links (active after the
|
maycmlee
reviewed
Oct 24, 2025
| ### Template Variable Values | ||
| Template variable values (values available via the template variable dropdowns) are populated based on what sources the widgets in the dashboard are using. For example, if your dashboard has widgets querying logs, you will only see values from logs. If your dashboard has widgets querying logs, metrics, and RUM, you will see values from logs, metrics, and RUM. | ||
|
|
||
| For most sources, template variable values will be relevant to your dashboard's global timeframe. If your dashboard's timeframe is set to the last 15 minutes, you will only see template variable values from the last 15 minutes. If your dashboard timeframe is set to a 24 hour period from last August, it will only show you values from that timeframe. |
There was a problem hiding this comment.
Suggested change
| For most sources, template variable values will be relevant to your dashboard's global timeframe. If your dashboard's timeframe is set to the last 15 minutes, you will only see template variable values from the last 15 minutes. If your dashboard timeframe is set to a 24 hour period from last August, it will only show you values from that timeframe. | |
| For most sources, template variable values are relevant to your dashboard's global timeframe. If your dashboard's timeframe is set to the last 15 minutes, only template variable values from the last 15 minutes are shown. If your dashboard timeframe is set to a 24 hour period from last August, only values from that timeframe are shown. |
There was a problem hiding this comment.
What does "24 hour period from last August" mean? I don't understand how that timeframe works.
There was a problem hiding this comment.
I was trying to give the example of a random day last August as an example. Would it be clearer to say "Last August 15 from 12 AM to 11:59 PM" ?
There was a problem hiding this comment.
Ah, yes, saying that specifically would be clearer. Thanks!
Co-authored-by: May Lee <may.lee@datadoghq.com>
Co-authored-by: May Lee <may.lee@datadoghq.com>
maycmlee
reviewed
Oct 24, 2025
Co-authored-by: May Lee <may.lee@datadoghq.com>
Co-authored-by: May Lee <may.lee@datadoghq.com>
maycmlee
approved these changes
Oct 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Update the dashboards template variables page to provide more information on how template variable values are populated, and the differences users might see as a result of certain data sources.
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes
N/A