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

Increase Alpha trace logs. #3679

Merged
merged 1 commit into from
Jul 17, 2019
Merged

Increase Alpha trace logs. #3679

merged 1 commit into from
Jul 17, 2019

Conversation

danielmai
Copy link
Contributor

@danielmai danielmai commented Jul 17, 2019

This change bumps up the number of logs per span to capture all the events from Server.Query instead of getting truncated logs in the trace data of up to 64 of the latest annotations.

When I load the 21-million movie data set and run a query to get all the movies directed by Steven Spielberg, Jaeger shows 232 logs for the query. With this change, the logs would be truncated if there are more than 256 annotations in a single span, leaving us to the same problem of possibly losing valuable info for a query trace.

{
  director(func: allofterms(name@en, "steven spielberg")) {
    name@en
    director.film {
      name@en
      initial_release_date
      country {
        name@en
      }
      starring {
        performance.actor {
          name@en
        }
        performance.character {
          name@en
        }
      }
      genre {
        name@en
      }
    }
  }
}

image


This change is Reviewable

Bump up the number of logs per span to capture all the events from
Server.Query.
@danielmai danielmai requested review from manishrjain and a team as code owners July 17, 2019 01:06
@dgraph-bot
Copy link
Contributor

dgraph-bot commented Jul 17, 2019 via email

Copy link

@gitlw gitlw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:lgtm:

Reviewable status: 0 of 1 files reviewed, all discussions resolved (waiting on @manishrjain)

@danielmai
Copy link
Contributor Author

Thanks @dgraph-bot 🤔 and @gitlw.

@danielmai danielmai merged commit 6dcfb1f into master Jul 17, 2019
@danielmai danielmai deleted the danielmai/max-logs-per-span branch July 17, 2019 17:48
dna2github pushed a commit to dna2fork/dgraph that referenced this pull request Jul 19, 2019
Bump up the number of logs per span to capture all the events
from Server.Query which can create a lot of logs.
danielmai added a commit that referenced this pull request Aug 13, 2019
Bump up the number of logs per span to capture all the events
from Server.Query which can create a lot of logs.
danielmai added a commit that referenced this pull request Aug 14, 2019
* Increase max trace logs per span in Alpha. (#3679)

Bump up the number of logs per span to capture all the events
from Server.Query which can create a lot of logs.

* Vendor in external dependencies necessary for OpenCensus.

We did not strictly vendor everything when v1.0.13 was originally released. Now
that we need to create a new patch release on top of Dgraph v1.0.13, we need to
bring back old dependencies that are necessary to create a new Dgraph binary. We
pick up versions for OpenCensus, Prometheus client, and gRPC that were released
before March 10, 2019 (the v1.0.13 release date).

* OpenCensus

  govendor fetch go.opencensus.io/...@v0.19.2

  v0.19.2 was released on Mar 21, 2019.

  I tried vendoring in v1.19.1 (released Mar 4) but it won't succeed with this
  error. v0.19.2 should be ok to use.

    Error: repo remote not secure
    Failed to fetch package "git.apache.org/thrift.git/lib/go/thrift"

* Prometheus client

  govendor fetch github.com/prometheus/client_golang/prometheus/...@v0.9.2

  v0.9.2 was released on Dec 6, 2018.

* gRPC

  govendor fetch google.golang.org/grpc/...@v1.13.0

  v1.13.0 was released on Jun 19, 2018.

  We already version lock gRPC to v1.13.0 in the contrib/release.sh.
danielmai added a commit that referenced this pull request Aug 30, 2019
Bump up the number of logs per span to capture all the events
from Server.Query which can create a lot of logs.
danielmai added a commit that referenced this pull request Aug 30, 2019
Cherry-picked from #3679.

Bump up the number of logs per span to capture all the events
from Server.Query which can create a lot of logs.

* release/v1.0: Add comment to MaxAnnotationsEventsPerSpan.
danielmai added a commit that referenced this pull request Sep 4, 2019
* Increase max trace logs per span in Alpha. (#3679)

Bump up the number of logs per span to capture all the events
from Server.Query which can create a lot of logs.

* Vendor in external dependencies necessary for OpenCensus.

We did not strictly vendor everything when v1.0.13 was originally released. Now
that we need to create a new patch release on top of Dgraph v1.0.13, we need to
bring back old dependencies that are necessary to create a new Dgraph binary. We
pick up versions for OpenCensus, Prometheus client, and gRPC that were released
before March 10, 2019 (the v1.0.13 release date).

* OpenCensus

  govendor fetch go.opencensus.io/...@v0.19.2

  v0.19.2 was released on Mar 21, 2019.

  I tried vendoring in v1.19.1 (released Mar 4) but it won't succeed with this
  error. v0.19.2 should be ok to use.

    Error: repo remote not secure
    Failed to fetch package "git.apache.org/thrift.git/lib/go/thrift"

* Prometheus client

  govendor fetch github.com/prometheus/client_golang/prometheus/...@v0.9.2

  v0.9.2 was released on Dec 6, 2018.

* gRPC

  govendor fetch google.golang.org/grpc/...@v1.13.0

  v1.13.0 was released on Jun 19, 2018.

  We already version lock gRPC to v1.13.0 in the contrib/release.sh.

(cherry picked from commit b196ca3)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants