You may also set `Prometheus` to enable them. For more information, refer to the details below.
## Self Observability
### Static IP or hostname
SkyWalking supports collecting telemetry data into the OAP backend directly. Users could check them out through UI or
GraphQL API.
SkyWalking supports exposing telemetry data representing OAP running status through Prometheus endpoint.
Users could set up OpenTelemetry collector to scrap and forward telemetry data to OAP server for further analysis,
eventually showing up UI or GraphQL API.
### Static IP or hostname
Add the following configuration to enable self-observability-related modules.
1. Set up prometheus telemetry.
...
...
@@ -101,6 +102,8 @@ For the full example for OpenTelemetry Collector configuration and recommended v
___
Users also could leverage the Prometheus endpoint for their own Prometheus and Grafana.
**NOTE**: Since Apr 21, 2021, the **Grafana** project has been relicensed to **AGPL-v3**, and is no longer licensed for Apache 2.0. Check the LICENSE details.
The following Prometheus + Grafana solution is optional rather than recommended.
Follow [OAP Self Observability Telemetry doc](backend-telemetry.md) to set up OAP and OpenTelemetry Collector.
## Self observability monitoring
Self observability monitoring provides monitoring of the status and resources of the OAP server itself. `oap-server` is a `Service` in OAP, and land on the `Layer: SO11Y_OAP`.