Subin Choi

related issue: https://github.com/knative/eventing/issues/6509

resolved by editing configmap ```yaml apiVersion: v1 kind: ConfigMap metadata: name: config-observability namespace: knative-serving labels: app.kubernetes.io/name: knative-serving app.kubernetes.io/component: observability app.kubernetes.io/version: "1.7.1" annotations: knative.dev/example-checksum: "fed4756e" data: metrics.backend-destination: prometheus metrics.request-metrics-backend-destination: prometheus ```

I think we need to add below block to **setting up prometheus** part. https://knative.dev/docs/serving/observability/metrics/collecting-metrics/#setting-up-prometheus ``` kubectl patch --namespace knative-serving configmap/config-observability \ --type merge \ --patch '{"data":{"metrics.backend-destination":"promethuus","metrics.request-metrics-backend-destination":"prometheus"}}' kubectl patch --namespace knative-serving...

@edsiper @leonardo-albertovich ping.

@edsiper @leonardo-albertovich I'm really happy to see the fluent-bit 2.0 release, and changes about the Loki Plugin https://github.com/fluent/fluent-bit/releases/tag/v2.0.0 with this PR merged, it'll be perfect!

Same here with knative-serving 1.7.1 https://github.com/knative/docs/issues/5217

@chrismellard I've got metrics working by editing `config-observability` as below. https://github.com/knative/serving/blob/main/config/core/configmaps/observability.yaml#L94 ```yaml # metrics.backend-destination field specifies the system metrics destination. # It supports either prometheus (the default) or opencensus. metrics.backend-destination:...

Or would it be wiser to create per-tenant `StorageClass`?

I've experienced this, `start.sh` returns error with default values @TAYTS are you still working on this?

@colearendt I'm facing similar problem, where I want to use 1 FSx volume (1200GiB) in multiple namespaces, with needs multiple PV and PVCs. How would using two PVs with same...