-
Notifications
You must be signed in to change notification settings - Fork 0
Ip check #16
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
base: main
Are you sure you want to change the base?
Ip check #16
Conversation
| IPv4: bool = True, | ||
| IPv6: bool = True): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are these here instead of in attributes? Seems like you should set these in ResourceAttributes. Not in initialize_telemetry.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I put them there to go along with collect_IP, but putting them in ResourceAttributes is probably cleaner considering that in most cases both of these values would be untouched
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Plus, doesn't the attr class actually do the retrieval work?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
technically no, it's a function defined in the attributes class but its called by initialize_telemetry. I will think about this though. I might be able to evaluate IP data before telemetry even gets initialized which would solve the blocking problem
No description provided.