Giter Club home page Giter Club logo

Comments (10)

SOF3 avatar SOF3 commented on July 17, 2024 1

The debugged issue in #133 is tracked in #127, but there is currently no fix yet because I haven't debugged the cause yet. I am on vacation right now; will have a look next week.

from kelemetry.

SOF3 avatar SOF3 commented on July 17, 2024

the query server depends on the kelemetry storage plugin server. it can't start until it successfully connects to the storage plugin server, which is run in the host by running make. it should be fixed as long as you start running the dev instance.

from kelemetry.

calvinxu avatar calvinxu commented on July 17, 2024

the query server depends on the kelemetry storage plugin server. it can't start until it successfully connects to the storage plugin server, which is run in the host by running make. it should be fixed as long as you start running the dev instance.

-- so base on the current setup for dev, how to work around it? or if I want to deploy using docker, does it support ?

from kelemetry.

SOF3 avatar SOF3 commented on July 17, 2024
  • make stack is for developers who are developing Kelemetry and want to test the functionality of Kelemetry on a test server whilst running the Kelemetry binary in terminal foreground. It works normally as long as you run make in your terminal.
  • make quickstart is for users who want to try out Kelemetry on a (kind) test cluster. This is the simplest setup, but it only works on a test cluster created in the script, not on a separate production cluster.
  • Use the helm chart to deploy Kelemetry for a real production cluster.

from kelemetry.

calvinxu avatar calvinxu commented on July 17, 2024
  • make stack is for developers who are developing Kelemetry and want to test the functionality of Kelemetry on a test server whilst running the Kelemetry binary in terminal foreground. It works normally as long as you run make in your terminal.

run "make" and start kelemetry, any advice on below logs?

INFO[0254] error retrieving resource lock default/kelemetry-diff-writer-leader-election-0: Get "https://127.0.0.1:6443/apis/coordination.k8s.io/v1/namespaces/default/leases/kelemetry-diff-writer-leader-election-0": dial tcp 127.0.0.1:6443: connect: connection refused  mod=kube
INFO[0254] error retrieving resource lock default/kelemetry-diff-writer-leader-election-0: Get "https://127.0.0.1:6443/apis/coordination.k8s.io/v1/namespaces/default/leases/kelemetry-diff-writer-leader-election-0": dial tcp 127.0.0.1:6443: connect: connection refused  mod=kube
INFO[0256] error retrieving resource lock default/kelemetry-diff-writer-leader-election-0: Get "https://127.0.0.1:6443/apis/coordination.k8s.io/v1/namespaces/default/leases/kelemetry-diff-writer-leader-election-0": dial tcp 127.0.0.1:6443: connect: connection refused  mod=kube
INFO[0258] error retrieving resource lock default/kelemetry-diff-writer-leader-election-0: Get "https://127.0.0.1:6443/apis/coordination.k8s.io/v1/namespaces/default/leases/kelemetry-diff-writer-leader-election-0": dial tcp 127.0.0.1:6443: connect: connection refused  mod=kube
INFO[0260] error retrieving resource lock default/kelemetry-diff-writer-leader-election-0: Get "https://127.0.0.1:6443/apis/coordination.k8s.io/v1/namespaces/default/leases/kelemetry-diff-writer-leader-election-0": dial tcp 127.0.0.1:6443: connect: connection refused  mod=kube
INFO[0260] error retrieving resource lock default/kelemetry-diff-writer-leader-election-0: Get "https://127.0.0.1:6443/apis/coordination.k8s.io/v1/namespaces/default/leases/kelemetry-diff-writer-leader-election-0": dial tcp 127.0.0.1:6443: connect: connection refused  mod=kube
INFO[0264] error retrieving resource lock default/kelemetry-diff-writer-leader-election-0: Get "https://127.0.0.1:6443/apis/coordination.k8s.io/v1/namespaces/default/leases/kelemetry-diff-writer-leader-election-0": dial tcp 127.0.0.1:6443: connect: connection refused  mod=kube
INFO[0264] error retrieving resource lock default/kelemetry-diff-writer-leader-election-0: Get "https://127.0.0.1:6443/apis/coordination.k8s.io/v1/namespaces/default/leases/kelemetry-diff-writer-leader-election-0": dial tcp 127.0.0.1:6443: connect: connection refused  mod=kube
INFO[0265] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:231: failed to list *v1.ConfigMap: Get "https://127.0.0.1:6443/api/v1/namespaces/default/configmaps?fieldSelector=metadata.name%3Dkelemetry-filter-config&limit=500&resourceVersion=0": dial tcp 127.0.0.1:6443: connect: connection refused  mod=kube
INFO[0265] pkg/mod/k8s.io/[email protected]/tools/cache/reflector.go:231: Failed to watch *v1.ConfigMap: failed to list *v1.ConfigMap: Get "https://127.0.0.1:6443/api/v1/namespaces/default/configmaps?fieldSelector=metadata.name%3Dkelemetry-filter-config&limit=500&resourceVersion=0": dial tcp 127.0.0.1:6443: connect: connection refused  mod=kube
INFO[0268] error retrieving resource lock default/kelemetry-diff-writer-leader-election-0: Get "https://127.0.0.1:6443/apis/coordination.k8s.io/v1/namespaces/default/leases/kelemetry-diff-writer-leader-election-0": dial tcp 127.0.0.1:6443: connect: connection refused  mod=kube
INFO[0268] error retrieving resource lock default/kelemetry-diff-writer-leader-election-0: Get "https://127.0.0.1:6443/apis/coordination.k8s.io/v1/namespaces/default/leases/kelemetry-diff-writer-leader-election-0": dial tcp 127.0.0.1:6443: connect: connection refused  mod=kube

from kelemetry.

SOF3 avatar SOF3 commented on July 17, 2024

Did you make kind before make stack?

from kelemetry.

SOF3 avatar SOF3 commented on July 17, 2024

You may also need to export KUBECONFIG to the kubeconfig for the new kind cluster (kind-tracetest).

from kelemetry.

calvinxu avatar calvinxu commented on July 17, 2024

run make and export KUBECONFIG, started and run normal, but it have the same issue to trace the audit-log

from kelemetry.

SOF3 avatar SOF3 commented on July 17, 2024

I can't reproduce this, and it is working correctly in the CI as well. Could you provide more detailed steps to reproduce this?

from kelemetry.

calvinxu avatar calvinxu commented on July 17, 2024

seems I mixed something up in the environment, just ignore my previous comments that mixed with "Audit log is not missed in the tracing data".
Just a quick question, is the issue "Audit log is not missed in the tracing data #133, that is on Jaeger UI only can see event, no audit logs displayed in the logs list of each span" currently tracked by #127 and target to be fixed by this PR? thanks.

from kelemetry.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.