wu-sheng commented on code in PR #11966:
URL: https://github.com/apache/skywalking/pull/11966#discussion_r1510104091


##########
oap-server/server-starter/src/main/resources/otel-rules/clickhouse/clickhouse-service.yaml:
##########
@@ -0,0 +1,155 @@
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements.  See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License.  You may obtain a copy of the License at
+#
+#     http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+# This will parse a textual representation of a duration. The formats
+# accepted are based on the ISO-8601 duration format {@code PnDTnHnMn.nS}
+# with days considered to be exactly 24 hours.
+# <p>
+# Examples:
+# <pre>
+#    "PT20.345S" -- parses as "20.345 seconds"
+#    "PT15M"     -- parses as "15 minutes" (where a minute is 60 seconds)
+#    "PT10H"     -- parses as "10 hours" (where an hour is 3600 seconds)
+#    "P2D"       -- parses as "2 days" (where a day is 24 hours or 86400 
seconds)
+#    "P2DT3H4M"  -- parses as "2 days, 3 hours and 4 minutes"
+#    "P-6H3M"    -- parses as "-6 hours and +3 minutes"
+#    "-P6H3M"    -- parses as "-6 hours and -3 minutes"
+#    "-P-6H+3M"  -- parses as "+6 hours and -3 minutes"
+# </pre>
+filter: "{ tags -> tags.job_name == 'clickhouse-monitoring' }" # The 
OpenTelemetry job name
+expSuffix:  tag({tags -> tags.host_name = 'clickhouse::' + 
tags.host_name}).service(['host_name'] , Layer.CLICKHOUSE)
+metricPrefix: meter_clickhouse
+metricsRules:
+  # Network
+  # Number of alive connections.
+  - name: connections_alive
+    exp: ClickHouseMetrics_KeeperAliveConnections.sum(['host_name'])

Review Comment:
   About this workflow, I want to ask, is every clickhouse node exposing an 
endpoint?
   If it's so, these metrics(service level) seem not correct. Let's say there 
are two Clickhouse nodes, each node has its the number of connections, OTEL 
will scrap two places and forward to OAP, then, without specific downsampling 
process, in one minute, the data from each node would overlap and override each 
other. How is this processed now?



-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to