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

Help: FOLLOWS_FROM reference doesn't link to other trace #1708

Closed
OlivierAlbertini opened this issue Aug 2, 2019 · 2 comments
Closed

Help: FOLLOWS_FROM reference doesn't link to other trace #1708

OlivierAlbertini opened this issue Aug 2, 2019 · 2 comments

Comments

@OlivierAlbertini
Copy link

OlivierAlbertini commented Aug 2, 2019

Hi,

Requirement - what kind of business use case are you trying to solve?

I try to make a FOLLOWS_FROM reference to another trace.
My first trace represent several API calls. The last call triggers a long running process (async process, 3-5seconds if everything is up)

Here my first trace:
Capture d’écran, le 2019-08-02 à 13 51 08

dsp-events-api calls the long running process.
Here the raw json of my first trace:

{
  "data": [
    {
      "traceID": "90bf511d794743cc8b49e7543a85b166",
      "spans": [
        {
          "traceID": "90bf511d794743cc8b49e7543a85b166",
          "spanID": "a9f2342543093bd9",
          "flags": 1,
          "operationName": "/api/city-services/formio-api/v1/validations/submission/5d4452ada2d1640017b22f4e",
          "references": [
            
          ],
          "startTime": 1564758714624000,
          "duration": 4120621,
          "tags": [
            {
              "key": "internal.span.format",
              "type": "string",
              "value": "proto"
            }
          ],
          "logs": [
            {
              "timestamp": 1564758718744000,
              "fields": [
                {
                  "key": "message.id",
                  "type": "float64",
                  "value": 1
                },
                {
                  "key": "message.type",
                  "type": "float64",
                  "value": 2
                }
              ]
            }
          ],
          "processID": "p1",
          "warnings": null
        },
        [...],
        {
          "traceID": "90bf511d794743cc8b49e7543a85b166",
          "spanID": "48815dcc0ad658f6",
          "flags": 1,
          "operationName": "POST /api/it-platforms/messaging/events/v1/events",
          "references": [
            {
              "refType": "CHILD_OF",
              "traceID": "90bf511d794743cc8b49e7543a85b166",
              "spanID": "a9f2342543093bd9"
            }
          ],
          "startTime": 1564758718353000,
          "duration": 388850,
          [...]
         },
         {
          "traceID": "90bf511d794743cc8b49e7543a85b166",
          "spanID": "7051c4226bd824fc",
          "flags": 1,
          "operationName": "/api/it-platforms/messaging/events/v1/events",
          "references": [
            {
              "refType": "CHILD_OF",
              "traceID": "90bf511d794743cc8b49e7543a85b166",
              "spanID": "48815dcc0ad658f6"
            }
          ],
          [...]
         }

Here my second trace:
Capture d’écran, le 2019-08-02 à 13 50 40
As you see, Jaeger UI shows <trace-without-root-span>
SN Worker DCI has a FOLLOWS_FROM reference to the dsp-events-api

{
  "data": [
    {
      "traceID": "e8cb698afce04831b912bd26d62467e8",
      "spans": [
        {
          "traceID": "e8cb698afce04831b912bd26d62467e8",
          "spanID": "11b73ddfe69dea3b",
          "flags": 1,
          "operationName": "create_service_request_task",
          "references": [
            {
              "refType": "FOLLOWS_FROM",
              "traceID": "90bf511d794743cc8b49e7543a85b166",
              "spanID": "48815dcc0ad658f6"
            }
          ],
          "startTime": 1564761895852000,
          "duration": 804337,
          [...]

Problem - what in Jaeger blocks you from solving the requirement?

Jaeger UI doesn't show the link between the two traces... Raw json for each trace seems fine.

Any open questions to address

  • Do you have a workaround ?
  • Do you see something that I'm doing wrong ?

Extra info

jaeger image version: jaegertracing/jaeger-collector:1.12
storage: elasticsearch: 6.8 oss
platform: Kubernetes

@OlivierAlbertini OlivierAlbertini changed the title FOLLOWS_FROM reference doesn't link to other trace Help: FOLLOWS_FROM reference doesn't link to other trace Aug 2, 2019
@yurishkuro
Copy link
Member

I think the solution to this would be once this ticket is implemented: jaegertracing/jaeger-ui#358

@yurishkuro
Copy link
Member

Please subscribe or reply to jaegertracing/jaeger-ui#358 for follow-up. I am closing this as duplicate. Feel free to re-open if you think it's something different.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants