Your issue is likely due to a different time precision in each datastream. Look at the example below.
Note the difference in
offsetInNanos for timestamps 1662866820 and 1662866830. When the offset is different in each datastream, Grafana Binary operation returns a NaN.
If this is helpful, consider accepting the answer.
Unable to connect AWS Managed grafana service to Private RDS instanceasked 3 months ago
Is there a way to alias the managed grafana endpoint in Route53?asked 10 months ago
Amazon Grafana Data Sourceasked 6 months ago
Auth0 with amazon managed grafanaasked 3 months ago
Can you edit the data in an Amazon QuickSight dashboard after it's published?Accepted Answerasked 2 years ago
AMG Grafana transform calculation problemasked 3 months ago
aws lambda stream newest data in local html/phpasked 6 months ago
Kinesis data stream iterator age spikesasked 4 months ago
Athena + CUR report in Grafana - How to calculate relative time (last month)?Accepted Answerasked 4 months ago
Kinesis Transformation Buffering from Data StreamAccepted Answerasked 6 months ago