You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be useful to be able to have a global set of tags which are applied to all supported resources. As a practical example, the ability to define a source repository, so the source of a dashboard can be located.
These would be provided in a provider argument, such as dashboard_tags and detector_tags.
The primary advantage is that users don't need to remember to update every resource individually (and in some cases they may not even be able to update them, such as in a module they only have read-only access to)
All the tags would then be appended on to the resource tags. This might be a map rather than a list, I'm not 100% familiar with how resource tags are used in SignalFx.
The text was updated successfully, but these errors were encountered:
Hi @tiedotguy,
Thanks a lot for bringing this up. I am PM and would be taking care of this issue.
We appreciate the practicality of defining a source repository for locating dashboard sources. We will consider adding provider arguments like "dashboard_tags" and "detector_tags" to help streamline the tag management process.
Your feedback is valuable, and we will further evaluate this feature. Feel free to share any additional insights or use cases. Thank you.
It would be useful to be able to have a global set of tags which are applied to all supported resources. As a practical example, the ability to define a source repository, so the source of a dashboard can be located.
These would be provided in a provider argument, such as
dashboard_tags
anddetector_tags
.The primary advantage is that users don't need to remember to update every resource individually (and in some cases they may not even be able to update them, such as in a module they only have read-only access to)
This might look something like:
All the tags would then be appended on to the resource tags. This might be a map rather than a list, I'm not 100% familiar with how resource tags are used in SignalFx.
The text was updated successfully, but these errors were encountered: