[Feature] How to monitor the configuration of the oap cluster itself via webapp?Self-Observability-OAP-Service No Data.

[FrankCy]

Search before asking

• I had searched in the issues and found no similar feature requirement.

Description

The telemetry information has been configured in the oapserver's application.yml according to the documentation.
The webapp's application.yml has also been configured with the same associations, and the relevant ports have been verified to return data.

• version

• Linux aarch64 20.04

• JDK：21 aarch64

• ES：8170

• ZK：3.4.14

• SkyWalking：10.0.1

• oapServer/application.yml Configuration snippet
  telemetry: selector: ${SW_TELEMETRY:prometheus} none: prometheus: host: ${SW_TELEMETRY_PROMETHEUS_HOST:192.168.163.196} port: ${SW_TELEMETRY_PROMETHEUS_PORT:12301} sslEnabled: ${SW_TELEMETRY_PROMETHEUS_SSL_ENABLED:false} sslKeyPath: ${SW_TELEMETRY_PROMETHEUS_SSL_KEY_PATH:""} sslCertChainPath: ${SW_TELEMETRY_PROMETHEUS_SSL_CERT_CHAIN_PATH:""}

• webapp/application.yml Configuration snippet
  collector: backend_service: ${SW_OAP_ADDRESS:http://192.168.163.196:12801}

• The curl version command restores the data normally
  curl -X POST http://192.168.163.196:12801/graphql -H "Content-Type: application/json" --data '{"query":"{ version }"}' {"data":{"version":"10.0.1-6a9d727"}}

• curl service error
  `curl -v -X POST http://192.168.163.196:12801/graphql -H "Content-Type: application/json" --data '{"query":"{ services { key name } }"}'
  Note: Unnecessary use of -X or --request, POST is already inferred.

• Trying 192.168.163.196:12801...
• TCP_NODELAY set
• Connected to 192.168.163.196 (192.168.163.196) port 12801 (#0)

POST /graphql HTTP/1.1
Host: 192.168.163.196:12801
User-Agent: curl/7.68.0
Accept: /
Content-Type: application/json
Content-Length: 37

• upload completely sent off: 37 out of 37 bytes
• Mark bundle as not supporting multiuse
  < HTTP/1.1 400 Bad Request
  < content-type: application/json
  < content-length: 205
  < server: Armeria/1.27.3
  < date: Wed, 22 Jan 2025 08:27:09 GMT
  <
• Connection #0 to host 192.168.163.196 left intact
  {"errors":[{"message":"Validation error (FieldUndefined@[services]) : Field 'services' in type 'Query' is undefined","locations":[{"line":1,"column":3}],"extensions":{"classification":"ValidationError"}}]}`

• 12301 can return data

However, the dashboard in the webapp ui can't display the oap data, and I can't find any documentation about it.

Use case

How can this be resolved? Monitor oap server metrics via SkyWalking's webapp. Instead of monitoring via external prometheus.

Related issues

No response

Are you willing to submit a pull request to implement this on your own?

• Yes I am willing to submit a pull request on my own!

Code of Conduct

• I agree to follow this project's Code of Conduct

[wu-sheng]

Do you check OAP logs? It seems your service does not boot completely.

[wu-sheng]

Learn from the showcase, profile so11y. It sets up all things, including otel collector with configurations. Like I said, k8s really helps a lot.

[FrankCy]

Thanks, unfortunately it still failed, I'll try deploying with docker again.✍️

[FrankCy]

If the docker build is fine, check the environment variables and core configuration again and you may find differences.💪

[wu-sheng]

It can't have issues. Because the demo.skywalking.apache.org is using the shoecase configurations through CD, no manual setup.

[FrankCy]

Hi, I solved my problem with the following steps:

1. Install opentelemetry on the node
   Download: https://github.com/open-telemetry/opentelemetry-collector-releases/releases
   2.Download the appropriate version according to the Linux version
2. After installation, create otel-collector-config.yaml and configure it.
   `receivers:
   otlp:
   protocols:
   grpc:
   endpoint: 0.0.0.0:4317
   http:
   endpoint: 0.0.0.0:4318
   prometheus:
   config:
   scrape_configs:
   - job_name: 'skywalking-so11y'
   scrape_interval: 5s
   static_configs:
   - targets: ['192.168.163.203:12301']
   labels:
   host_name: http://192.168.163.203:12301
   service: oap-server

processors:
batch:

exporters:
otlp:
endpoint: 192.168.163.203:11801
tls:
insecure: true

service:
pipelines:
traces:
receivers: [otlp]
processors: [batch]
exporters: [otlp]
metrics:
receivers: [prometheus]
processors: [batch]
exporters: [otlp]
logs:
receivers: [otlp]
processors: [batch]
exporters: [otlp]`

4. Start otelcol
   . /otelcol --config=otel-collector-config.yaml

Once it is up and running, login to the skywalking webapp at the following address:
http://192.168.163.203:9000/dashboard/SO11Y_OAP/ServiceInstance/Self-Observability-OAP-Instance

[FrankCy]

Sorry for the correction, but the version of zookeeper is 3.8.4.