profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/naseemkullah/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.
Naseem naseemkullah SRE @ToricLabs

helm/charts 15241

⚠️(OBSOLETE) Curated applications for Kubernetes

fluent/helm-charts 114

Helm Charts for Fluentd and Fluent Bit

naseemkullah/gcp-accountant 13

A tool to identify high cost resources in GCP at a granular level

naseemkullah/ansible-prometheus-node-exporter 0

Ansible role for deploying Prometheus node exporter

naseemkullah/autoscaler 0

Autoscaling components for Kubernetes

naseemkullah/aws-cdk 0

The AWS Cloud Development Kit is a framework for defining cloud infrastructure in code

naseemkullah/aws-solutions-constructs 0

The AWS Solutions Constructs Library is an open-source extension of the AWS Cloud Development Kit (AWS CDK) that provides multi-service, well-architected patterns for quickly defining solutions

naseemkullah/Backblaze-Docker 0

Docker image with backblaze cli

naseemkullah/chart-testing 0

CLI tool for linting and testing Helm charts

issue commentaws/aws-cdk

aws-s3-deployment cloudfront invalidatation/waiter race condition

Thought I would mention I've had this happen today twice in row, once upon stack update and the once upon stack rollback, resulting in an UPDATE_ROLLBACK_FAILED state requiring a manual Continue update rollback.

naseemkullah

comment created time in 2 days

issue openedgetsentry/sentry-javascript

add convencience method startActiveSpan

To avoid the following when custom instrumenting:

Sentry.getCurrentHub()
    .getScope()
    ?.getTransaction()
    ?.startChild(spanContext);
    ```

```js
function startActiveSpan(
  spanContext?:
    | Pick<
        SpanContext,
        | "description"
        | "status"
        | "tags"
        | "op"
        | "data"
        | "startTimestamp"
        | "endTimestamp"
      >
    | undefined
) {
  return Sentry.getCurrentHub()
    .getScope()
    ?.getTransaction()
    ?.startChild(spanContext);
}

N.B. we may want to use the internal getActiveTransation() under the hood, and also expose that as well as it is another great convencience method

created time in 3 days

issue commentgetsentry/sentry

zero duration spans without warnings

thanks!

naseemkullah

comment created time in 5 days

issue closedgetsentry/sentry

zero duration spans without warnings

Problem Statement

I would like to add "markers" of when events occured to my traces. Currently to do so I must create a span manually pass in the startTimestamp and endTimestamp with the same value (time of event).

In the UI this span gets a warning "Equal start and end times", would there be a way to disable the warning?

Solution Brainstorm

Add option to disable warning on 0ms spans, or create a new api method for setting markers.

closed time in 5 days

naseemkullah

issue commentgetsentry/sentry

zero duration spans without warnings

performance.mark() works great, before closing, is this explicitly stated in the docs somewhere?

naseemkullah

comment created time in 5 days

issue commentgetsentry/sentry

zero duration spans without warnings

Thanks @Zylphrex, FWIW I am unable to find any mention of mark let alone the {op: "mark} trick in the linked custom instrumentation documentation.

The second point is also very useful, I will see if I can swap our the custom sentry instrumentation code with performance.mark("myCustomEvent") and have that automatically picked up by sentry.

naseemkullah

comment created time in 5 days

issue openedgetsentry/sentry

zero duration spans without warnings

Problem Statement

I would like to add "markers" of when events occured to my traces. Currently to do so I must create a span manually pass in the startTimestamp and endTimestamp with the same value (time of event).

In the UI this span gets a warning "Equal start and end times", would there be a way to disable the warning?

Solution Brainstorm

Add option to disable warning on 0ms spans, or create a new api method for setting markers.

created time in 5 days

startedpragmaticivan/nestjs-otel

started time in 7 days

issue commentaws/aws-cdk

aws-s3-deployment cloudfront invalidatation/waiter race condition

Confirming that in my case the validation occurs when it should, but the waiter just never gets the memo and fails the deployment after 10 minutes.

naseemkullah

comment created time in 8 days

delete branch naseemkullah/sentry-docs

delete branch : patch-3

delete time in 9 days

delete branch naseemkullah/sentry-docs

delete branch : patch-2

delete time in 9 days

push eventnaseemkullah/sentry-docs

Naseem

commit sha badd2885d5421e04f17d92a0f4a73ed31fe26267

use try/catch/finally for custom span mgmt

view details

push time in 9 days

push eventnaseemkullah/sentry-docs

Naseem

commit sha 2e9e581c29da89f4fa9ac3b31ffaa85ca1a2d5f8

use try/catch/finally for custom span mgmt

view details

push time in 9 days

fork naseemkullah/sentry-docs

The new place for the sentry documentation (and tools to build it)

https://docs.sentry.io

fork in 9 days

fork naseemkullah/nestjs-pino

Platform agnostic logger for NestJS based on Pino with REQUEST CONTEXT IN EVERY LOG

fork in 11 days

startediamolegga/nestjs-pino

started time in 11 days

PullRequestReviewEvent

issue commentaws/aws-cdk

aws-s3-deployment cloudfront invalidatation/waiter race condition

In this case, the most plausible hypothesis is that CloudFront is actually taking longer than 10 min to invalidate the files in some cases. We can try to reduce the chance of this happening by increasing the waiting time, but Lambda has a maximum timeout of 15 min. Beyond that, it's not clear to me what else we can do. In any case, contributions are welcome!

it has happened twice in recent days, next time it occurs i will try to confirm this, iirc the first time this happened i checked and I saw the invalidation event had occurred almost immediately yet the waiter did not see that (that's why i thought it might be a race condition). Will confirm though!

naseemkullah

comment created time in 15 days

startedevanshortiss/env-var

started time in 16 days

pull request commentActionsDesk/lfs-warning

v3

Thanks @ppremk

naseemkullah

comment created time in 16 days

pull request commentawslabs/aws-solutions-constructs

do not create cloudfront log bucket if disabled

@biffgaut was this included in 1.118.0?

naseemkullah

comment created time in 16 days

PR merged fluent/helm-charts

Reviewers
[fluent-bit] update to v1.8.6
  • Updated Fluent Bit image to v1.8.6
  • Bumped chart patch version
+3 -3

1 comment

1 changed file

stevehipwell

pr closed time in 17 days

push eventfluent/helm-charts

Steve Hipwell

commit sha 8471a92cf71906072efd4b0da257c3eb65d61212

[fluent-bit] update to v1.8.6 Signed-off-by: Steve Hipwell <steve.hipwell@gmail.com>

view details

Naseem

commit sha a504442ecc0963bdf927bb88ae19fd097e3f8908

Merge pull request #155 from stevehipwell/fluent-bit-v1-8-6 [fluent-bit] update to v1.8.6

view details

push time in 17 days

pull request commentfluent/helm-charts

[fluent-bit] Update to v1.8.5

Cheers @stevehipwell

stevehipwell

comment created time in 18 days

push eventfluent/helm-charts

Steve Hipwell

commit sha 29c56553ca9cfce5bb2c3f1cbbb9c3206b75ae7e

[fluent-bit] Update to v1.8.5 Signed-off-by: Steve Hipwell <steve.hipwell@gmail.com>

view details

Naseem

commit sha c7e883d2439ef54de326d8d32e08197c05c6a5f4

Merge pull request #154 from stevehipwell/fluent-bit-v1-8-5 [fluent-bit] Update to v1.8.5

view details

push time in 18 days

PR merged fluent/helm-charts

Reviewers
[fluent-bit] Update to v1.8.5
  • Updated Fluent Bit image to v1.8.5
  • Bumped chart patch version
+3 -3

1 comment

1 changed file

stevehipwell

pr closed time in 18 days

pull request commentjaegertracing/helm-charts

Check for using "networking.k8s.io/v1" is incorrect

Thanks for raising this issue @hardik-fareye, we've just released 0.46.6 where @cwrau imported bitnami's https://github.com/bitnami/charts/tree/master/bitnami/common to standardize on api versioning logic, could you please try it out, if it still fails please rebase to get the latest changes. Cheers

hardik-fareye

comment created time in 18 days