-
Notifications
You must be signed in to change notification settings - Fork 381
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
Environment configuration not being picked up #1032
Comments
+1 Also seeing an issue since updating to 0.35.1 from 0.34.2. We had the following configuration line
I'm trying multiple iterations to get env to stick.
wasn't working for me either. |
@kelvin-acosta @mattmcf I was able to reproduce this issue. If you put We're working on a bugfix for this now. |
Thanks @delner. I'll try that now. |
@delner That also worked for me locally. I'll ship a fix for us. Thank you! |
@kelvin-acosta Also for your configuration, Datadog.configure do |c|
c.service = Runtime.app_name
c.env = 'stage'
c.tracer.hostname = 'my-host'
c.tracer.port = 1234
c.use :rails
end |
We identified a cause for this and have a bug fix #1034 in progress; will keep you posted. |
@kelvin-acosta @mattmcf thank you again for this issue report! |
Confirmed that this fixes my issue. Thank you for the prompt fix! |
We recently updated our
dd-trace-rb
to0.35.1
and were using this configuration beforeonce we updated we found that
set_tags
was erroring since the method has been removedAfter looking at the changelog for
0.34.0
we then updated our configuration toBut this doesn't seem to work. All of our traces show up with
env:none
in datadog. Wondering if we misconfigured something or if this is simply a bug.Please let me know if I can provide anything else to help. Thanks!
The text was updated successfully, but these errors were encountered: