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

Support uploading logs from edge devices behind gateway #21

Open
jacqueskang opened this issue Feb 24, 2022 · 1 comment
Open

Support uploading logs from edge devices behind gateway #21

jacqueskang opened this issue Feb 24, 2022 · 1 comment

Comments

@jacqueskang
Copy link

Please provide us with the following information:

This issue is for a: (mark with an x)

- [ ] bug report -> please search issues before submitting
- [x] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Any log messages given by the failure

Expected/desired behavior

It seems that currently version of ELMS only supports retrieving logs from top-layer edge devices. InvokeUploadModuleLogs function invokes UploadModuleLogs with SasUrl of azure blob storage's public endpoint. According to this link to retrieve logs from devices behind gateway it should use something like "https://$upstream:8000/myBlobStorageName/myContainerName?SAS_key" instead.

It would be great if InvokeUploadModuleLogs could identify edge devices behind gateway (e.g., having a parent device) and generates appropriate sasUrl for them.

OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Versions

Mention any other details that might be useful


Thanks! We'll be in touch soon.

@jacqueskang jacqueskang changed the title Support uploading logs from edge devices behind transparent gateway Support uploading logs from edge devices behind gateway Feb 24, 2022
@rashmisingh622
Copy link

rashmisingh622 commented Apr 8, 2022

This is fixed.. the last PR that was merged(fixing the event hub api version) did it I guess. I had applied the change in my local branch, but I guess it wasn't working because the deployment template was referring to the template in this repository... Thank you so much!

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

No branches or pull requests

2 participants