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

instrument basic event tracking #89

Closed
drewbanin opened this issue Aug 3, 2016 · 1 comment
Closed

instrument basic event tracking #89

drewbanin opened this issue Aug 3, 2016 · 1 comment
Milestone

Comments

@drewbanin
Copy link
Contributor

No description provided.

@jthandy jthandy modified the milestone: 0.5.0 Aug 12, 2016
@drewbanin drewbanin modified the milestone: 0.4.1 Aug 18, 2016
@drewbanin drewbanin modified the milestone: 0.4.2 Aug 27, 2016
@drewbanin
Copy link
Contributor Author

drewbanin commented Sep 14, 2016

  • opt-out config (goes in profile.yml)
  • Ping fivetran about snowplow python events
  • unstructured events
  • ip
  • user uuid
  • version
  • hashed node names - start (1 per model run)
  • hashed node names - end (1 per model run)
  • top-level error message (if errored) sans stack trace

"job" events
"node" events

  • should also work for dbt test
  • should be able to discern between "dry" runs and "real" runs (in job)
  • uuid for job, models use this id
  • debug, init, compile, run... these are all jobs/instantiations/invocation/etc

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

No branches or pull requests

2 participants