profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/punya/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Punya Biswal punya Google Boston, MA Building @opentelemetry at @google. Formerly @palantir, @asappinc, @tetrascience.

punya/spark-gradle-test-example 18

Example demonstrating a Scala project that builds using Gradle, produces a shadow jar suitable for spark-submit, and has tests using Scalatest

open-telemetry/opentelemetry-go-vanityurls 3

Vanityurls config for go.opentelemetry.io subdomain

punya/golang-samples 1

Sample apps and code written for Google Cloud in the Go programming language.

punya/blog 0

Punya's tech blog

Pull request review commentopen-telemetry/opentelemetry-go-contrib

AWS X-Ray config module for Lambda instrumentation

+# Recommended Configurations for OpenTelemetry AWS Lambda Instrumentation with AWS X-Ray++[![Go Reference][goref-image]][goref-url]+[![Apache License][license-image]][license-url]++This module provides recommended configuration options for [`AWS Lambda Instrumentaton`](https://github.com/open-telemetry/opentelemetry-go-contrib/tree/main/instrumentation/github.com/aws/aws-lambda-go/otellambda) when using [AWS X-Ray](https://aws.amazon.com/xray/).++## Installation++```bash+go get -u go.opentelemetry.io/contrib/instrumentation/github.com/aws/aws-lambda-go/otellambda/xrayconfig+```++## Usage++Create a sample Lambda Go application instrumented by the `otellambda` package such as below.++```go+package main++import (+	"context"+	"fmt"+	"github.com/aws/aws-lambda-go/lambda"+	"go.opentelemetry.io/contrib/instrumentation/github.com/aws/aws-lambda-go/otellambda"+)++type MyEvent struct {+	Name string `json:"name"`+}++func HandleRequest(ctx context.Context, name MyEvent) (string, error) {+	return fmt.Sprintf("Hello %s!", name.Name ), nil+}++func main() {+	lambda.Start(otellambda.WrapHandlerFunction(HandleRequest))+}+```++Now configure the instrumentation with the provided options to export traces to AWS X-Ray via [the OpenTelemetry Collector](https://github.com/open-telemetry/opentelemetry-collector) running as a Lambda Extension. Instructions for running the OTel Collector as a Lambda Extension can be found in the [AWS OpenTelemetry Documentation](https://aws-otel.github.io/docs/getting-started/lambda).

In addition to uploading traces to X-Ray, does this library also

  • extract trace context from X-Amzn-Trace-Id headers on inbound requests
  • apply an X-Amzn-Trace-Id header to outbound requests It may be worth documenting clearly in the README.
bhautikpip

comment created time in 3 days

PullRequestReviewEvent

Pull request review commentopen-telemetry/opentelemetry-go-contrib

End to end tracing support - Lambda

+# OpenTelemetry AWS Lambda Resource Detector for Golang++[![Go Reference][goref-image]][goref-url]+[![Apache License][license-image]][license-url]++This module detects resource attributes available in AWS Lambda.++## Installation++```bash+go get -u go.opentelemetry.io/contrib/detectors/aws/lambda+```++## Usage++Create a sample Lambda Go application such as below.++```go+package main++import (+	"github.com/aws/aws-lambda-go/lambda"+	sdktrace "go.opencensus.io/otel/sdk/trace"+	lambdadetector "go.opentelemetry.io/contrib/detectors/aws/lambda"+)++func main() {+	detector := lambdadetector.NewResourceDetector()+	res, err := detector.Detect(context.Background())+	if err != nil {+		fmt.Printf("failed to detect lambda resources: %v\n", err)+	}++	tp := sdktrace.NewTracerProvider(+		sdktrace.WithResource(res),+	)+	lambda.Start(<some lambda handler>)

Does the example need either otel.SetTracerProvider(tp) or passing tp explicitly into the Lambda handler? Otherwise the variable is unused.

bhautikpip

comment created time in 10 days

PullRequestReviewEvent
PullRequestReviewEvent

Pull request review commentopen-telemetry/opentelemetry-go-contrib

End to end tracing support - Lambda

+# OpenTelemetry AWS Lambda Resource Detector for Golang++[![Go Reference][goref-image]][goref-url]+[![Apache License][license-image]][license-url]++This module detects resource attributes available in AWS Lambda.++## Installation++```bash+go get -u go.opentelemetry.io/contrib/detectors/aws/lambda+```++## Usage++Create a sample Lambda Go application such as below.++```go+package main++import (+	"github.com/aws/aws-lambda-go/lambda"+	sdktrace "go.opencensus.io/otel/sdk/trace"+	lambdadetector "go.opentelemetry.io/contrib/detectors/aws/lambda"+)++func main() {+	detector := lambdadetector.NewResourceDetector()+	res, err := detector.Detect(context.Background())+	if err != nil {+		fmt.Printf("failed to detect lambda resources: %v\n", err)+	}++	tp := sdktrace.NewTracerProvider(+		sdktrace.WithResource(res),+	)+	lambda.Start(<some lambda handler>)+}+```++Now your `TracerProvider` will have the following resource attributes and attach them to new spans:++| Resource Attribute | Example Value |+| --- | --- |+| `cloud.provider` | aws+|`cloud.region` | us-east-1 +|`faas.name` | MyLambdaFunction +|`faas.version` | $LATEST++Of note, `faas.id` and `cloud.account.id` are not set by the Lambda resource detector because they are not available outside a Lambda invocation. For this reason, when using the AWS Lambda Instrumentation these attributes are set as additional span attributes.

Could this be solved through lazy initialization?

bhautikpip

comment created time in 3 days

PullRequestReviewEvent

delete branch punya/opentelemetry-collector-contrib

delete branch : healthcheckextension

delete time in 11 days

PR closed open-telemetry/opentelemetry-collector-contrib

Migrate healthcheckextension to contrib

This is a POC for the migration approach to use in https://github.com/open-telemetry/opentelemetry-collector/issues/3474. Note that the healthcheckextension is currently slated to remain in the "core" repo, so the point of this PR is explicitly to understand the tradeoffs in the approach through a minimal example, not to migrate an individual component.

Approach

  1. Import the entire history of the core repo into a branch of the contrib repo.
  2. Delete everything except the healthcheckextension from that branch.
  3. Merge the imported branch into the working branch (created off of main).
  4. Perform fixups such as adding go.mod, Makefile, adding a component.

Consequences

  1. 👍🏽 Full commit history on files that come in as part of this PR.
  2. 👎🏽 Lots of unnecessary commits are now in this repo's history, even though they don't appear in any file blames.
  3. 👍🏽 No duplication of commit history in future PRs (see "subtree" alternative below for more details).
  4. 👎🏽 References to Github notions (such as PRs and issues) from historical commits are still broken.

Alternative 1 (subtree)

  1. In the core repo, construct a "split subtree" branch corresponding to the healthcheckextension.
  2. Do a "subtree import" of that branch into the correct target location.
  3. Fixups.

Consequences

  1. 👍🏽 Only relevant commits ingested in this PR
  2. 👎🏽 Future imports will create duplicate commits
  3. 👎🏽 References to Github notions (such as PRs and issues) from historical commits are still broken.

Alternative 2 (copy files without history)

  1. Copy the relevant files from the core repo into the contrib repo.
  2. Fixups.

Consequences

  1. 👎🏽 All Git-level and Github-level history is lost
+2384 -0

8 comments

16 changed files

punya

pr closed time in 11 days

push eventpunya/gopsutil

Punya Biswal

commit sha 5169bfe02d1586e2f0d92118a8967c820cada63c

Update mem/mem_bsd.go Co-authored-by: shirou <shirou.faw@gmail.com>

view details

push time in 13 days

issue commentGoogleCloudPlatform/opentelemetry-operations-go

Potential memory leak in metric exporter

@ryanlaycock just checking in - are you still experiencing the OOM? We're ver interested in figuring out if this library is related in any way, so please share any information you can from the crash.

ryanlaycock

comment created time in 15 days

issue closedGoogleCloudPlatform/opentelemetry-operations-js

GKE resources support

OpenTelemetry GCP detectors supports GKE resources but unfortunately those seems not to be shipped by Cloud Trace Exporter.

closed time in 15 days

emmekappa

issue commentopen-telemetry/opentelemetry-collector-contrib

Problems to use otel-collector as log pipeline

Hi @gillg! Would you mind linking the previous issues relevant to this topic? Also, it would be helpful to call out specific enhancements that you're looking for, with as much precision and concrete use cases as possible.

gillg

comment created time in 15 days

issue closedopen-telemetry/opentelemetry-collector-contrib

Unable to get github.com/open-telemetry/opentelemetry-collector-contrib/pkg/translator/jaeger

Describe the bug

I'm looking to use the translation code for Jaeger and unable to include it in my project due to a versioning issue.

Steps to reproduce

❯ go get github.com/open-telemetry/opentelemetry-collector-contrib/pkg/translator/jaeger
go get: github.com/open-telemetry/opentelemetry-collector-contrib/pkg/translator/jaeger@v0.0.0-20210829183103-2d1672ce1a53 requires
	github.com/open-telemetry/opentelemetry-collector-contrib/internal/coreinternal@v0.0.0-00010101000000-000000000000: invalid version: unknown revision 000000000000

What did you expect to see? I expected the code to download and update my go.mod for including the new module.

What did you see instead?

An error describing the revision mentioned in the go.mod for the package is not known.

What version did you use?

I'd use any version that contained this translation code.

What config did you use?

N/A

Environment OS: Archlinux Compiler: go 1.17

Additional context

If the code exists elsewhere in a different version, please advise.

closed time in 15 days

zalegrala

issue commentopen-telemetry/opentelemetry-collector-contrib

Unable to get github.com/open-telemetry/opentelemetry-collector-contrib/pkg/translator/jaeger

@zalegrala could you try again? v0.34.0 of both these modules was tagged soon after you created this issue, and it looks like it sets the dependencies correctly.

Please reopen this issue if the issue continues to appear.

zalegrala

comment created time in 15 days

issue commentopen-telemetry/opentelemetry-collector-contrib

Need to add k8sEventReceiver

Could you add some details about the use case for this receiver, and what sort of OTel data it will produce?

rockb1017

comment created time in 15 days

issue closedopen-telemetry/opentelemetry-collector-contrib

Not able to get resource metrics as labels in prometheus exporter

Describe the bug Not able to get resource metrics using below config in prometheus exporter

    resource_to_telemetry_conversion:
      enabled: true

Steps to reproduce otel-collector-config.yml looks like

receivers:
  otlp:
    protocols:
      grpc:
      http:
  hostmetrics:
    collection_interval: 10s
    scrapers:
      cpu:
      memory:

processors:
  batch:
    send_batch_size: 1000
    timeout: 10s
  memory_limiter:
    # Same as --mem-ballast-size-mib CLI argument
    ballast_size_mib: 683
    # 80% of maximum memory up to 2G
    limit_mib: 1500
    # 25% of limit up to 2G
    spike_limit_mib: 512
    check_interval: 5s

extensions:
  health_check: {}
  zpages: {}
exporters:
  prometheus:
    endpoint: "0.0.0.0:8889"
    resource_to_telemetry_conversion:
      enabled: true

service:
  extensions: [health_check, zpages]
  pipelines:
    metrics:
      receivers: [otlp, hostmetrics]
      processors: [batch]
      exporters: [prometheus]

Current Behaviour

system_cpu_time{cpu="cpu0",state="idle"} 9.76013346e+06
system_cpu_time{cpu="cpu0",state="interrupt"} 0
system_cpu_time{cpu="cpu0",state="nice"} 13.32
system_cpu_time{cpu="cpu0",state="softirq"} 6048.61
system_cpu_time{cpu="cpu0",state="steal"} 13547.32
system_cpu_time{cpu="cpu0",state="system"} 73781.09
system_cpu_time{cpu="cpu0",state="user"} 282649.92
system_cpu_time{cpu="cpu0",state="wait"} 457.76
system_cpu_time{cpu="cpu1",state="idle"} 9.75988229e+06
system_cpu_time{cpu="cpu1",state="interrupt"} 0
system_cpu_time{cpu="cpu1",state="nice"} 4.29
system_cpu_time{cpu="cpu1",state="softirq"} 5887.16
system_cpu_time{cpu="cpu1",state="steal"} 13489.81
system_cpu_time{cpu="cpu1",state="system"} 73566.51
system_cpu_time{cpu="cpu1",state="user"} 282017.25
system_cpu_time{cpu="cpu1",state="wait"} 608.4

What did you expect to see? I expected to see resource metrics as labels exported.

What version did you use? Running otel-collector version 0.26.0 and 0.34.0, both seem to have the same problem

Environment OS: darwin19.0, Mac and Linux

closed time in 15 days

ankitnayan

issue commentopen-telemetry/opentelemetry-collector-contrib

Not able to get resource metrics as labels in prometheus exporter

@ankitnayan collector receivers (including the host metrics receiver) don't automatically detect/attach host-related resource attributes -- see https://github.com/open-telemetry/opentelemetry-collector/issues/871 for details. You can add the resource detection processor to your pipeline if you need that behavior.

Please feel free to reopen this issue if you run into other problems.

ankitnayan

comment created time in 15 days

issue commentopen-telemetry/opentelemetry-collector-contrib

Not work HTTP receiver (404 response)

Can you also include the full HTTP response you receive from the collector, and anything that's logged during that request?

andreatosato

comment created time in 16 days

PullRequestReviewEvent

pull request commentshirou/gopsutil

Add swapdevices method

Hi @shirou. I work with @tbarker25 and am continuing his work in #1131. I've incorporated your feedback in that PR, please let me know if you're okay with merging it.

tbarker25

comment created time in 16 days

PR opened shirou/gopsutil

Add swapdevices method (continued from #1120)

Continued from #1120. I work with @tbarker25 and am continuing his work in this PR, because he's going to be busy for a few weeks.

+542 -10

0 comment

15 changed files

pr created time in 16 days

create barnchpunya/gopsutil

branch : tbarker25-swap-contd

created branch time in 16 days

fork punya/gopsutil

psutil for golang

fork in 16 days

push eventGoogleCloudPlatform/opentelemetry-operations-js

WhiteSource Renovate

commit sha 2d3b1908120a6807bea04ef87abe7d9fa7c18750

chore(deps): update dependency typescript to v4.4.2 (#322) * chore(deps): update dependency typescript to v4.4.2 * Explicitly annotate catch variables as any Co-authored-by: Punya Biswal <punya@google.com>

view details

push time in 16 days

PR merged GoogleCloudPlatform/opentelemetry-operations-js

Reviewers
chore(deps): update dependency typescript to v4.4.2 dependencies

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
typescript (source) 4.3.5 -> 4.4.2 age adoption passing confidence

Release Notes

<details> <summary>Microsoft/TypeScript</summary>

v4.4.2

Compare Source

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

Downloads are available on:

</details>


Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

+45 -45

2 comments

13 changed files

renovate-bot

pr closed time in 16 days

PullRequestReviewEvent

push eventrenovate-bot/opentelemetry-operations-js

Punya Biswal

commit sha c3bd33f34e877f45b65736f3da39f4e7a9e15d01

Explicitly annotate catch variables as any

view details

push time in 16 days

push eventGoogleCloudPlatform/opentelemetry-operations-js

WhiteSource Renovate

commit sha 8166b7e285a4738792c0ecffe9e046f27e901c3d

chore(deps): update all non-major dependencies (#323)

view details

push time in 16 days