Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for ServiceMap with Deligated GW #11088

Closed
mhkarimi1383 opened this issue Aug 10, 2024 · 10 comments
Closed

Support for ServiceMap with Deligated GW #11088

mhkarimi1383 opened this issue Aug 10, 2024 · 10 comments
Assignees
Labels
kind/feature New feature triage/rotten closed due to lack of information for too long, rejected feature...

Comments

@mhkarimi1383
Copy link

Description

I have setup Kuma with Kong in my cluster and It's working great But I set setup grafana I notice that the provided dashboard is empty since they are working with envoy specific metrics

@mhkarimi1383 mhkarimi1383 added kind/feature New feature triage/pending This issue will be looked at on the next triage meeting labels Aug 10, 2024
@slonka
Copy link
Contributor

slonka commented Aug 12, 2024

triage: is that the Kong is not showing up in the Service Map or are you expecting something else to show up in the metrics?

@slonka slonka added triage/needs-information Reviewed and some extra information was asked to the reporter and removed triage/pending This issue will be looked at on the next triage meeting labels Aug 12, 2024
@mhkarimi1383
Copy link
Author

@slonka ServiceMap is empty

@lukidzi
Copy link
Contributor

lukidzi commented Aug 19, 2024

Triage: Could you provide steps to reproduce? Also, could you post policies that you've applied? @mhkarimi1383

@jakubdyszkiewicz jakubdyszkiewicz added triage/needs-reproducing Someone else should try to reproduce this and removed triage/needs-information Reviewed and some extra information was asked to the reporter labels Sep 2, 2024
@jakubdyszkiewicz
Copy link
Contributor

Triage: let's check on our side. Just a simple deployment with MeshMetrics.

@slonka slonka assigned slonka and unassigned slonka Sep 16, 2024
@slonka slonka self-assigned this Oct 7, 2024
@slonka
Copy link
Contributor

slonka commented Oct 7, 2024

Could not reproduce with 2.8.3:

image

Steps:

  1. Install kuma
kumactl install control-plane | kubectl apply -f -
  1. Install observability
kumactl install observability | kubectl apply -f -
  1. Add traces and metrics:
echo 'apiVersion: kuma.io/v1alpha1
kind: MeshMetric
metadata:
  name: metrics-default
  namespace: kuma-system
  labels:
    kuma.io/mesh: default
spec:
  targetRef:
    kind: Mesh
  default:
    sidecar:
      includeUnused: true
      profiles:
        appendProfiles:
        - name: Basic
    backends:
    - type: Prometheus
      prometheus:
        port: 5670
        path: "/metrics"
' | kubectl apply -f -
apiVersion: kuma.io/v1alpha1
kind: MeshTrace
metadata:
  name: default
  namespace: kuma-system
  labels:
    kuma.io/mesh: default # optional, defaults to `default` if unset
spec:
  targetRef:
    kind: Mesh
  default:
    backends:
      - type: Zipkin
        zipkin:
          url: http://jaeger-collector.mesh-observability:9411/api/v2/spans

@slonka slonka added triage/pending This issue will be looked at on the next triage meeting and removed triage/needs-reproducing Someone else should try to reproduce this labels Oct 7, 2024
@mhkarimi1383
Copy link
Author

There is nothing is docs mentioned that I have to install extra things for observability

@slonka
Copy link
Contributor

slonka commented Oct 7, 2024

triage: did you install the observability stack from kumactl or some other way? If you setup grafana yourself you need to install the plugin manually https://github.com/kumahq/kuma-grafana-datasource

@slonka slonka added triage/needs-information Reviewed and some extra information was asked to the reporter and removed triage/pending This issue will be looked at on the next triage meeting labels Oct 7, 2024
@lukidzi
Copy link
Contributor

lukidzi commented Oct 21, 2024

@mhkarimi1383 Hi, have you had a chance to review the question above?

@mhkarimi1383
Copy link
Author

I have set up the plugin manually but I have not enabled anything in my Kuma to add observability
But docs need some improvement I think

@jakubdyszkiewicz
Copy link
Contributor

Triage: we checked with this and it's fine https://kuma.io/docs/2.9.x/guides/otel-metrics/

@jakubdyszkiewicz jakubdyszkiewicz added triage/rotten closed due to lack of information for too long, rejected feature... and removed triage/needs-information Reviewed and some extra information was asked to the reporter labels Oct 28, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature triage/rotten closed due to lack of information for too long, rejected feature...
Projects
None yet
Development

No branches or pull requests

4 participants