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 2022/03/19 10:33:53 UTC

[GitHub] [skywalking] Cool-Coding edited a comment on issue #8707: [Bug] first_aggregation and second_aggregation in fetcher-prom-rules/self.yaml are wrong

Cool-Coding edited a comment on issue #8707:
URL: https://github.com/apache/skywalking/issues/8707#issuecomment-1072979576


   > Thanks for reporting. I think you should fix `otel-oc-rules/oap.yaml` as well.
   > 
   > I have assigned this to you, wait for your pull request. FYI @wankai123
   
   ok, I will look at the  `otel-oc-rules/oap.yaml`  and pull a request.
   I have a question about oap.yaml because I don't use otel-oc-rules.  My understanding is that the  `otel-oc-rules/oap.yaml` play the same role as `fetcher-prom-rules/self.yaml` used to observe oap.  if so, we can't  make both of  them work in applicaion.yml. is that true?
   
   I have see the `aggregation` metric in  `otel-oc-rules/oap.yaml`. I found that the duration in `self.yaml` is 'PT5M', but the duration in `oap.yaml` is 'PT1M'.  The unit description of   `Aggreation`  chart in `ui-initialized-templates/self-observability.yml` is 'Per minute'. so I will also change the duration in `self.yaml` to 'PT1M' in the pull request.


-- 
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.

To unsubscribe, e-mail: notifications-unsubscribe@skywalking.apache.org

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