Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Jean Jordaan
    @jean
    @tigrannajaryan thanks! That is what I expected but the website (/about) is a bit scary: "OpenTelemetry captures metrics, distributed traces, resource metadata, and logs (logging support is incubating now)"
    My guess is that that means logs in a more formal sense than the usage I mentioned.
    Jean Jordaan
    @jean
    Regarding sending events, I guess we might use https://www.github.com/open-telemetry/opentelemetry-js/tree/master/packages%2Fopentelemetry-web .. We're currently using https://github.com/DataDog/browser-sdk -- if the Collector understands the format that sends, we might just point it at the Collector and keep on using it.
    Jean Jordaan
    @jean
    Am I mistaken to be looking for a Collector->Snowplow exporter? Is Snowplow an alternative to the Collector?
    4 replies
    Przemek Maciolek
    @pmm-sumo
    Did the schedule for Log SIG change? I don't see it present in the calendar anymore. Me and @zenmoto got on but there was nobody else present. Didn't have any specific topics for today, just curious if I missed something
    Tigran Najaryan
    @tigrannajaryan
    @pmm-sumo Log SIG meeting is biweekly, it should be in the calendar for the next week, Wed, 3pm PT.
    2 replies
    Pavan
    @pathardepavan
    I looked at https://docs.datadoghq.com/tracing/connect_logs_and_traces/python Tried to add the traceid and spanid in the logs. But the traces and spans generated by opentelemetry and dd are different. Is there a way to get the context traceid/spanid natively in Python ?
    1 reply
    Tigran Najaryan
    @tigrannajaryan
    @/all to allow people from more eastern times to join the SIG meeting I am moving it to an earlier hour, 10am PT starting from Oct 28. If the new time doesn't work for some people we will need to look into alternating times.
    1 reply
    Tigran Najaryan
    @tigrannajaryan
    @/all I am cancelling the Log SIG meeting today. Christian and Przemek can't attend, David and I don't have any topics and I don't see any topics in the agenda doc either. Everybody in Otel is focused on traces and metrics release. Let's meet next week (check the calendar, the time is different).
    Mark
    @MarkSeufert
    Hey guys, I'm working on the Logging SDK and I have ran into a design choice problem. The .NET logging implementation, which I was using as reference, has the LoggerProvider contains a list of processors that all the Logger's use when a logging statement is called. However, this prevents different loggers from writing to different processors. An alternate approach that I'm considering is having each Logger contain its own list of processors, such that different loggers can write to different processors. This would be useful if, for example, we wanted a console logger that only writes to console, and a separate logger that writes to a different destination (ElasticSearch for example). Does anyone have any objections to this second approach? Thanks in advance :)
    1 reply
    Alex Van Boxel
    @alexvanboxel
    I have a question about the Log data model. The usage of Name, in the appendix ( https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/logs/data-model.md#appendix-a-example-mappings ) sometimes Name is describing a single Event (example: EventLogs, CloudTrail, ...) and sometimes a collection of entries (example: Google Cloud Logging). Looking at the description "Short event identifier that does not contain varying parts.", it feels that Google Cloud Logging is wrong... but I see a need to have some kind of grouping key (like : LogName). What's everyone's idea around this?
    6 replies
    Amol
    @Amolstar_twitter
    I have used the Open Telemetry based API's for Metrics collection and tracing. Do we have any sample that can be referred to see how open telemetry based logging can be done? Any pointers/document would help. Thanks.
    5 replies
    Otis Gospodnetić
    @otisg
    Hi. What's considered best practice - separate logs and metrics exporters or one that can export both logs and metrics?
    I see the Logs GA definition at https://github.com/open-telemetry/oteps/blob/master/text/logs/0130-logs-1.0ga-definition.md . Is there a rough estimate for when Logs GA might happen? 2020 or 2021? :)
    1 reply
    ayushmpb95
    @ayushmpb95
    Hi Guys,
    Has it been decided that what logging libraries would be supported per language, for example for golang will it be Zap or logrus etc?
    Also, I understand this is an ongoing project, but would really appreciate if someone gives an idea that it will involve schema validation as well? Or that heavy lifting will be taken on by the collector? Or none of these are requirements.
    3 replies
    Would it also be possible to directly plugin ECS(Elastic Common Schema) for example https://github.com/elastic/ecs-logging-go-zap into first party application?
    Thanks!
    realwoobinlee
    @realwoobinlee
    Hello guys :) just a short question: is there any release date planned for first logging Support? just a rough estimation would be fine (ex. First quarter 2021) Thanks!
    2 replies
    Anurag Gupta
    @agup006
    Hey friends, I see on GitHub the meeting time is 13:00 PT and in the calendar invite it shows as 10:00 PT
    5 replies
    Tigran Najaryan
    @tigrannajaryan
    @/all I will be on PTO starting from tomorrow until Jan 4. I will not attend the SIG meeting on Dec 23. I am not sure what the attendance is going to look like given the holidays, but I will keep the meeting on the calendar in case there is people who want to meet.
    Christian Beedgen
    @kumoroku
    happy holidays! FWIW I will also be out next week. maybe folks can speak up if there's a topic they want to discuss.
    Tigran Najaryan
    @tigrannajaryan
    David is also out, so I think keeping it on the calendar is pointless. I will cancel on Dec 23. Happy holidays and see you all next year!
    Tigran Najaryan
    @tigrannajaryan
    All, here is a separate issue about Telemetry Schema: open-telemetry/opentelemetry-specification#1324
    Please comment.
    gagansingh355
    @gagansingh355

    Hey guys, I wanted to ask has anyone used @Include keyword on fluentbit in otel's main yml file(otel-collector-config.yml)? I getting issue in including a config file, can someone please provide format for this?
    My file for now is:
    extensions:
    fluentbit:
    executable_path: /opt/td-agent-bit/bin/td-agent-bit
    tcp_endpoint: 127.0.0.1:8006
    @INCLUDE /usr/local/go/src/opentelemetry-collector/examples/tracing/temp.conf

    receivers:
    fluentforward:
    endpoint: 0.0.0.0:8006

    gagansingh355
    @gagansingh355
    One more doubt, I have created my custom exporter and fluenbit is extension and fluentforwarder is the receiver. Can someone please confirm in what format will I receive logs at exporter side?
    1 reply
    Bryan Wu
    @bryan-wu-gitter
    Hi folks. I'm looking to obfuscate specific fields in logs. Is there any built-in functionality for obsfucation in the .NET SDK or pre-exisiting solutions I can reference? Thanks
    gagansingh355
    @gagansingh355
    Has anyone used @INCLUDE in fluent-bit extension in OTEL collector?
    Kiran
    @kiranpatel11
    Do libraries in different languages support "log" specifications ? https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/overview.md
    Omer Katz
    @thedrow
    Unfortunately Python still doesn't
    Kiran
    @kiranpatel11
    mostly I see the support for tracing and metrics, but not sure of log specs adherence yet
    Omer Katz
    @thedrow
    I don't see an API for it yet anyway
    But maybe I missed it
    Tigran Najaryan
    @tigrannajaryan
    No, most languages don't support logs yet. There is some minimal support in Java.
    Morgan McLean
    @mtwo
    FYI you'll see more focus on the logging APIs after tracing and metrics reach GA. Most of the community is working on traces and metrics first, as these were the original focus of the project - logs will be next after that!
    Tigran Najaryan
    @tigrannajaryan
    @/all there is now a Slack channel for logs https://app.slack.com/client/T08PSQ7BQ/C01N5UCHTEH
    I suggest to move to Slack unless there are objections and people want to stay on Gitter.
    Christian Beedgen
    @kumoroku
    great, I am supportive of going to Slack!
    Reiley Yang
    @reyang
    +1 on CNCF Slack
    Tigran Najaryan
    @tigrannajaryan
    I submitted a PR to update the link from Gitter to Slack: open-telemetry/community#665
    Let's move to Slack, everyone.