Skip to content
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

Event Metadata fields mapping is wrong. #263

Closed
Sachin4403 opened this issue Sep 28, 2022 · 0 comments · Fixed by #265
Closed

Event Metadata fields mapping is wrong. #263

Sachin4403 opened this issue Sep 28, 2022 · 0 comments · Fixed by #265

Comments

@Sachin4403
Copy link
Contributor

Hello Team,

Whenever CPE will try to connect to talaria, it will be sending the metadata parameters in convey headers and talaria will decode the convey header and persist it in memory. now the problem is there in parodus or talaria because parodus will be sending the key and talaria is expecting another key.

Here is a detailed view of the problem

Here parodus will be building convey header. with these all keys.

hw-model
hw-serial-number
hw-manufacturer
hw-last-reboot-reason
fw-name
webpa-last-reconnect-reason
webpa-protocol
webpa-interface-used
boot-time-retry-wait
boot-time

and in talaria we are expecting a few other fields.

boot-time
hw-model
hw-manufacturer
hw-serial-number
hw-last-reboot-reason
fw-name
last-reconnect-reason
protocol

now there is a mismatch between the fields. we need to fix it either in parodus or in talaria.

cc: @schmidtw

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant