-
-
Notifications
You must be signed in to change notification settings - Fork 20
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
Diagnostic processor should call diag less frequently #202
Comments
this one might be related. |
pritamghanghas
added a commit
that referenced
this issue
Aug 4, 2022
* added slow refersh in case everything is ok.
4 tasks
pritamghanghas
added a commit
that referenced
this issue
Aug 5, 2022
* added slow refersh in case everything is ok.
pritamghanghas
added a commit
that referenced
this issue
Aug 5, 2022
* added slow refersh in case everything is ok.
pritamghanghas
added a commit
that referenced
this issue
Aug 5, 2022
…calls fix: Diagnostic processor should call diag less frequently #202
Merged
4 tasks
This can be merged to production too |
this is already merged.
…On Thu, 11 Aug 2022 at 15:38, KevinWassermann94 ***@***.***> wrote:
This can be merged to production too
—
Reply to this email directly, view it on GitHub
<#202 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABU3SVY77JPBIL7CFXKZ64TVYTGKRANCNFSM52WF6OFQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
checked again. hm-config hash carrying this is already in production closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
currently hm-config calls diagnostic json end point every 60 seconds. In hm-config LedProcessor is its only user.
Side effects of running diagnostics this freqenty:
Acceptance Criteria:
The text was updated successfully, but these errors were encountered: