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
Description
I have about 200 edge instances deployed and they all have the same dashboard deployed, tailored to the edge data. I want the name of the panel to be for example: "${EdgeName} - Energy".
How could I do it without creating a panel for each instance?
Thanks in advance.
Disclaimer
We appreciate your contribution whether it is a bug report, feature request, or pull request with improvement (hopefully). Please comply with the Community ethics policy, and do not expect us to answer your requests immediately. Also, do not treat GitHub issues as a support channel.
The text was updated successfully, but these errors were encountered:
Currently, there is no built-in functionality to display the Edge name in a specific widget out-of-the-box. However, this is a great feature idea for the future.
For now, you can use the following workaround: create an alias to fetch all edges entities and display the name of the fetched edges. On the cloud, this alias will randomly select one of your edges and display its name. On the edge, this alias will select the exact name of the dedicated edge.
Here are screenshots of the configuration of the dashboard and alias on the cloud:
Screenshot of the first edge:
Screenshot of the second edge:
As you can see, the title of the dashboard differs from edge to edge. I hope this approach can meet your goals for the moment.
Component
Description
I have about 200 edge instances deployed and they all have the same dashboard deployed, tailored to the edge data. I want the name of the panel to be for example: "${EdgeName} - Energy".
How could I do it without creating a panel for each instance?
Thanks in advance.
Disclaimer
We appreciate your contribution whether it is a bug report, feature request, or pull request with improvement (hopefully). Please comply with the Community ethics policy, and do not expect us to answer your requests immediately. Also, do not treat GitHub issues as a support channel.
The text was updated successfully, but these errors were encountered: