-
Notifications
You must be signed in to change notification settings - Fork 641
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
Datadog exporter to use service_name from Resource #574
Comments
Please assign thanks! 😊 |
This issue was marked stale due to lack of activity. It will be closed in 30 days. |
@ericmustin |
@lzchen ah, ty for the ping. I'll push something up here this week, should be quick. Lost track of it after the original pr sorry about that |
This issue was marked stale due to lack of activity. It will be closed in 30 days. |
@ericmustin |
@lzchen Hey, sorry. I had some time scheduled for this but then I uh, quit my employer. So, unfort i have a bunch of $newjob stuff to do and this isnt a huge priority for me. @majorgreys Would probably be the right person here for all things Datadog moving forward, or at least, he can put you in touch with the appropriate ppl. fwiw i think there are plans to simply deprecate this exporter as the datadog-agent now accepts otlp natively (experimental), but i'll defer on that to @majorgreys |
Thanks for the reply. I'll unassign you for the time being. |
@majorgreys @ericmustin if the plan is to deprecate it, should we open a ticket to track that? You might want to add a deprecation notice and release once more and after that remove the package from the repo. |
From this comment
The text was updated successfully, but these errors were encountered: