We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello,
When coding Autohide markup in title in .json of dashboard like this :
"name": "My Visualization !PU(autohide):",
If vizualisation is not masqued, I can see in title "!PU(autohide):", that is not very nice.
Is it possible to hide this text "!PU(autohide):" ?
In the exemple here, this text is not visible, how to do that : https://github.com/dynatrace-oss/DynatraceDashboardPowerups#Disclaimer Out of memory containers !PU(autohide): The visualization title is "Out of memory containers", not "Out of memory containers !PU(autohide):".
Out of memory containers !PU(autohide):
How to do that please ?
PS : I tryed to put code in "customName" section but it doesn't work : "customName": "Out of memory containers !PU(autohide):",
"customName": "Out of memory containers !PU(autohide):",
Thank you for advance.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hello,
When coding Autohide markup in title in .json of dashboard like this :
"name": "My Visualization !PU(autohide):",
If vizualisation is not masqued, I can see in title "!PU(autohide):", that is not very nice.
Is it possible to hide this text "!PU(autohide):" ?
In the exemple here, this text is not visible, how to do that :
https://github.com/dynatrace-oss/DynatraceDashboardPowerups#Disclaimer
Out of memory containers !PU(autohide):
The visualization title is "Out of memory containers", not "Out of memory containers !PU(autohide):".
How to do that please ?
PS : I tryed to put code in "customName" section but it doesn't work :
"customName": "Out of memory containers !PU(autohide):",
Thank you for advance.
The text was updated successfully, but these errors were encountered: