-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
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
Log metadata is overwritten in a single-process environment #1708
Comments
|
It turns out both are true. The issue doesn't affect Airnode deployed to AWS (v0.9 or v0.10), but does affect airnode-client:0.9.2
airnode-deployer:0.9.2 and airnode-deployer:0.10.0AWS logs:
And the I did notice that among the two
And stream 2 had the opposite Providers:
|
For unclear reasons, when using the
|
I presume this is because when running Airnode locally it doesn't really run as multiple processes (as the cloud version). So, when we call |
That makes sense, which would imply we need to pass provider and chainId for each log. |
After more work, I recommend pushing this issue to the Airnode release containing the single lambda Airnode. As @amarthadan mentions above, log metadata e.g. |
This is an issue that needs to be solved when implementing #1478 |
Description
When there are multiple Providers specified for a chain, the Airnode logs report incorrect
Provider
names within the log metadata, see the example below.Version
Airnode v0.9, v0.10, master.
Present Behaviour
In
config.json
there are two providers:Yet in the logs (in multiple places, below is one example), the metadata
Provider
is incorrect for one (they both sayProvider:goerliTestnet1
at the end of the line on the far right):This makes troubleshooting confusing as it is not clear what provider the logs are attributable to.
Expected Behaviour
Log metadata should report the correct Provider names.
Steps to reproduce
Run Airnode with more than one Provider.
The text was updated successfully, but these errors were encountered: