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

bad device value need detail and response error message #655

Open
sdvdxl opened this issue Dec 15, 2023 · 5 comments
Open

bad device value need detail and response error message #655

sdvdxl opened this issue Dec 15, 2023 · 5 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@sdvdxl
Copy link

sdvdxl commented Dec 15, 2023

🚀 Feature Request

Relevant Package [REQUIRED]

when device send bad value, we need know what happend.

Description [REQUIRED]

For example, if I define a property as temperature, the data type is float64, but the data sent is "a", then it should return this error through a topic, not just in the service log, and the log does not print the data of which device send the data.

image

Describe the solution you'd like

  1. add a topic to response the error message
  2. log detail, add device info

Describe alternatives you've considered

Have you considered any alternative solutions or workarounds?
@sdvdxl sdvdxl added the enhancement New feature or request label Dec 15, 2023
@jiekechoo
Copy link

@sdvdxl Please provide your device profile and device configuration.

@cloudxxx8 cloudxxx8 added the help wanted Extra attention is needed label Dec 16, 2023
@cloudxxx8
Copy link
Member

cloudxxx8 commented Dec 16, 2023

The log message can be improved from here

commandValue, err := newResult(resource, asyncValue)
if err != nil {
driver.Logger.Errorf("[Incoming listener] Incoming data ignored: %v", err)
return
}

@lindseysimple
Copy link

lindseysimple commented Jan 17, 2024

Describe the solution you'd like

  1. add a topic to response the error message
  2. log detail, add device info

Hi @sdvdxl , based on the Device WG discussion on 16 Jan, 2024

  1. For the 1st solution add a topic to response the error message you suggested, since this will be a new feature for EdgeX, we need a UCR for the community to review.

    If you think this feature would be helpful for you and across EdgeX, please go ahead and submit a UCR. Please note that UCR is a high level requirements documentation, and we don't need implementation details on it.

    Another workaround for now is to use some external tools such as Logstash to centralize and monitor the service logs.

  2. For the 2nd solution log detail, add device info, can you add some description on what's the other details you would like to be included in the log except for the device name, and it would be great if you have some bandwidth to work on this!

Thanks and please let me know if you have any further questions.

@sdvdxl
Copy link
Author

sdvdxl commented Jan 17, 2024

For the 2nd solution log detail, add device info, can you add some description on what's the other details you would like to be included in the log except for the device name, and it would be great if you have some bandwidth to work on this!

maybe include device name, device profile?

@cloudxxx8
Copy link
Member

Please feel free to opne a new PR to include them

@jumpingliu jumpingliu moved this to New Issues in Technical WG Jul 30, 2024
@cloudxxx8 cloudxxx8 moved this from New Issues to Icebox in Technical WG Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
Status: Icebox
Development

No branches or pull requests

4 participants