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.

Sign up for GitHub

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

Jump to bottom

Support Knative eventing in vHive #164

Closed
ustiugov opened this issue Mar 9, 2021 · 1 comment · Fixed by #177
Closed

Support Knative eventing in vHive #164

ustiugov opened this issue Mar 9, 2021 · 1 comment · Fixed by #177
Assignees
@shyamjesal
Labels
enhancement New feature or request
Projects
vHive Roadmap
Milestone
Support function ...

Comments

@ustiugov
Copy link
Member

ustiugov commented Mar 9, 2021

No description provided.

@ustiugov ustiugov created this issue from a note in vHive Roadmap (In progress) Mar 9, 2021
@ustiugov ustiugov added the enhancement New feature or request label Mar 9, 2021
@ustiugov ustiugov added this to the Support function composition milestone Mar 9, 2021
@shyamjesal
Copy link
Collaborator

Source: https://knative.dev/docs/eventing/accessing-traces/

The following demonstrates how to trace requests in Knative Eventing with Zipkin, using the TestBrokerTracing End-to-End test.
For this example, assume the following details:

  • Everything happens in the includes-incoming-trace-id-2qszn namespace.

  • The Broker is named br.

  • There are two Triggers that are associated with the Broker:

    • transformer - Filters to only allow events whose type is transformer. Sends the event to the Kubernetes Service transformer, which will reply with an identical event, except the replied event's type will be logger.
    • logger - Filters to only allow events whose type is logger. Sends the event to the Kubernetes Service logger.

  • An event is sent to the Broker with the type transformer, by the Pod named sender.

Given the above, the expected path and behavior of an event is as follows:

  1. sender Pod sends the request to the Broker.

  2. Go to the Broker's ingress Pod.

  3. Go to the imc-dispatcher Channel (imc stands for InMemoryChannel).

  4. Go to both Triggers.

    1. Go to the Broker's filter Pod for the Trigger logger. The Trigger's filter ignores this event.

    2. Go to the Broker's filter Pod for the Trigger transformer. The filter does pass, so it goes to the Kubernetes Service pointed at, also named transformer.

      1. transformer Pod replies with the modified event.

      2. Go to an InMemory dispatcher.

      3. Go to the Broker's ingress Pod.

      4. Go to the InMemory dispatcher.

      5. Go to both Triggers.

        1. Go to the Broker's filter Pod for the Trigger transformer. The Trigger's filter ignores the event.

        2. Go to the Broker's filter Pod for the Trigger logger. The filter passes.

          1. Go to the logger Pod. There is no reply.

This is a screenshot of the trace view in Zipkin. All the red letters have been added to the screenshot and correspond to the expectations earlier in this section:
image

@shyamjesal shyamjesal linked a pull request Mar 17, 2021 that will close this issue
Add Knative eventing in default cluster setup #177
Merged
vHive Roadmap automation moved this from In progress to Done Mar 17, 2021
HermioneKT added a commit that referenced this issue Jan 31, 2024
@HermioneKT
# This is a combination of 252 commits.
3c6919f 
parent 6674807
author HermioneKT <hermionegrangerkt@gmail.com> 1706694164 +0800
committer HermioneKT <hermionegrangerkt@gmail.com> 1706694164 +0800

test

# This is the commit message #157:

test

# This is the commit message #159:

test

# This is the commit message #160:

test

# This is the commit message #161:

test

# This is the commit message #162:

test

# This is the commit message #163:

test

# This is the commit message #164:

tesT

# This is the commit message #165:

test

# This is the commit message #166:

test

# This is the commit message #167:

test

# This is the commit message #168:

test

# This is the commit message #169:

test

# This is the commit message #170:

test

# This is the commit message #171:

Test

# This is the commit message #172:

test

# This is the commit message #173:

test

# This is the commit message #174:

test

# This is the commit message #175:

test

# This is the commit message #176:

test

# This is the commit message #177:

test

# This is the commit message #178:

test

# This is the commit message #179:

test

# This is the commit message #180:

test

# This is the commit message #181:

test

# This is the commit message #182:

test

# This is the commit message #183:

test

# This is the commit message #184:

test

# This is the commit message #185:

test

# This is the commit message #186:

test

# This is the commit message #187:

test

# This is the commit message #188:

test

# This is the commit message #189:

test

# This is the commit message #190:

Test

# This is the commit message #191:

Test

# This is the commit message #192:

test

# This is the commit message #193:

Test

# This is the commit message #194:

test

# This is the commit message #195:

test

# This is the commit message #196:

test

# This is the commit message #197:

test

# This is the commit message #198:

test

# This is the commit message #199:

Test

# This is the commit message #200:

test

# This is the commit message #201:

test

# This is the commit message #202:

Test

# This is the commit message #203:

test

# This is the commit message #204:

test

# This is the commit message #205:

test

# This is the commit message #206:

test

# This is the commit message #207:

test

# This is the commit message #208:

test

# This is the commit message #209:

test

# This is the commit message #210:

test

# This is the commit message #211:

Test

# This is the commit message #212:

test

# This is the commit message #213:

Test

# This is the commit message #214:

Test

# This is the commit message #215:

Test

# This is the commit message #216:

test

# This is the commit message #217:

Test

# This is the commit message #218:

test

# This is the commit message #219:

test

# This is the commit message #220:

test

# This is the commit message #221:

test

# This is the commit message #222:

test

# This is the commit message #223:

test

# This is the commit message #224:

test

# This is the commit message #225:

test

# This is the commit message #226:

test

# This is the commit message #227:

test

# This is the commit message #228:

test

# This is the commit message #229:

Test

# This is the commit message #230:

test

# This is the commit message #231:

test

# This is the commit message #232:

test

# This is the commit message #233:

test

# This is the commit message #234:

Test

# This is the commit message #235:

test

# This is the commit message #236:

test

# This is the commit message #237:

test

# This is the commit message #238:

test

# This is the commit message #239:

test

# This is the commit message #240:

test

# This is the commit message #241:

test

# This is the commit message #242:

test

# This is the commit message #243:

test

# This is the commit message #244:

test

# This is the commit message #245:

test

# This is the commit message #246:

test

# This is the commit message #247:

test

# This is the commit message #248:

test

# This is the commit message #249:

test

# This is the commit message #250:

test

# This is the commit message #251:

test

# This is the commit message #252:

test
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shyamjesal shyamjesal

Labels
enhancement New feature or request
Projects
vHive Roadmap
  
Done
Milestone
Support function composition
Development

Successfully merging a pull request may close this issue.

Add Knative eventing in default cluster setup vhive-serverless/vHive
2 participants
@ustiugov @shyamjesal