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
The graphana dashboard use names like namespace, workerType etc which seems to be in consistent with tags originated from server (frontend, matcher etc) .i.e https://github.com/temporalio/temporal/blob/master/common/metrics/tags.go (the canary tests which i presumes runs from the worker and the temporal namespace which is only in server shows info here)
But however real namespaces do not endup showing data here because the tag names mismatch (see java sdk and go sdk tags
these do not appear in grafana as the tag names are little different e.g Namespace in sdk and namespace in server, WorkflowType in server etc.
Now should the namespace tag not be same every where.
Now what iam confused is is this discrepancy between server and sdk code , or is it bug in the graphana dashoard json file!
The text was updated successfully, but these errors were encountered:
Expected Behavior
Expect to see sdk metrics in the sdk dahboard
Actual Behavior
The sdk metrics do not get populated in this dashboard
Steps to Reproduce the Problem
Additional Info
The graphana dashboard use names like namespace, workerType etc which seems to be in consistent with tags originated from server (frontend, matcher etc) .i.e https://github.com/temporalio/temporal/blob/master/common/metrics/tags.go (the canary tests which i presumes runs from the worker and the temporal namespace which is only in server shows info here)
But however real namespaces do not endup showing data here because the tag names mismatch (see java sdk and go sdk tags
these do not appear in grafana as the tag names are little different e.g Namespace in sdk and namespace in server, WorkflowType in server etc.
Now should the namespace tag not be same every where.
Now what iam confused is is this discrepancy between server and sdk code , or is it bug in the graphana dashoard json file!
The text was updated successfully, but these errors were encountered: