You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by GitBox <gi...@apache.org> on 2021/05/05 11:16:56 UTC

[GitHub] [skywalking] JayeshMuley opened a new issue #6896: Dynamically changing the Alarm Threshold not picked up.

JayeshMuley opened a new issue #6896:
URL: https://github.com/apache/skywalking/issues/6896


   Please answer these questions before submitting your issue.
   
   - Why do you submit this issue?
   - [ X] Question or discussion
   - [ ] Bug
   - [ ] Requirement
   - [ ] Feature or performance improvement
   
   
   I am using Skywalking 8.5 and need to change the alarm setting dynamically, And for this i changed the Service Instance Response Time Rule Threshold value. But it didn't picked up . 
   
   As per the document alarm.default.alarm-settings this needs to be set. But not sure how this parameter to be set in Application.yml, so that dynamic changes can be reflected. 
   
   Please guide.
   
   Thanks and Regards,
   Jayesh Muley


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [skywalking] wu-sheng commented on issue #6896: Dynamically changing the Alarm Threshold not picked up.

Posted by GitBox <gi...@apache.org>.
wu-sheng commented on issue #6896:
URL: https://github.com/apache/skywalking/issues/6896#issuecomment-832751445


   > This means the Alarm should picked up the latest value setup in alarm-setting.yml. But in my case I need to restart OAP server in order to reflect the latest value.
   
   No, it doesn't mean that. The dynamic content should be updated through the dynamic config center. Not through the original file. https://skywalking.apache.org/docs/main/v8.5.0/en/setup/backend/dynamic-config/


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [skywalking] wu-sheng closed issue #6896: Dynamically changing the Alarm Threshold not picked up.

Posted by GitBox <gi...@apache.org>.
wu-sheng closed issue #6896:
URL: https://github.com/apache/skywalking/issues/6896


   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [skywalking] wu-sheng commented on issue #6896: Dynamically changing the Alarm Threshold not picked up.

Posted by GitBox <gi...@apache.org>.
wu-sheng commented on issue #6896:
URL: https://github.com/apache/skywalking/issues/6896#issuecomment-832635072


   I am not sure about your question. `Application.yml` has nothing related to the alarm. And the dynamic alarm setting is actually overriding the whole alarm context. 
   
   > As per the document alarm.default.alarm-settings this needs to be set
   
   The value is the latest content of all alarm rules. Same format as `alarm-settings.yml`. 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [skywalking] JayeshMuley commented on issue #6896: Dynamically changing the Alarm Threshold not picked up.

Posted by GitBox <gi...@apache.org>.
JayeshMuley commented on issue #6896:
URL: https://github.com/apache/skywalking/issues/6896#issuecomment-832720175


   This means the Alarm should picked up the latest value setup in alarm-setting.yml.  But in my case I need to restart OAP server in order to reflect the latest value.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org