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
While working on #3743 we have discovered that the url label was missed in the move from the external teraslice-exporter to the one built into terafoundation.
The url where an instance of teraslice lives on the network is controlled at the k8s level (if I understand this correctly), so either needs to be provided as an environmental variable or added as a field to the terafoundation. If added to the terafoundation, do we include prom_metrics in the key? This makes sense with our current use case, but the url could be needed in other contexts in the future that are not prom metrics related.
Another option is to have the dashboard add the url labels to each metric after they are scraped by grabbing the url from the Ingress.
The text was updated successfully, but these errors were encountered:
While working on #3743 we have discovered that the
url
label was missed in the move from the externalteraslice-exporter
to the one built intoterafoundation
.The url where an instance of teraslice lives on the network is controlled at the k8s level (if I understand this correctly), so either needs to be provided as an environmental variable or added as a field to the terafoundation. If added to the terafoundation, do we include
prom_metrics
in the key? This makes sense with our current use case, but the url could be needed in other contexts in the future that are not prom metrics related.Another option is to have the dashboard add the url labels to each metric after they are scraped by grabbing the url from the Ingress.
The text was updated successfully, but these errors were encountered: