srikanthccv

		using var meter = new Meter("my-meter");
		var providerBuilder = Sdk.CreateMeterProviderBuilder().AddMeter(meter.Name);
		providerBuilder
        .AddOtlpExporter((exporterOptions, metricReaderOptions) =>
			{
                metricReaderOptions.PeriodicExportingMetricReaderOptions = new PeriodicExportingMetricReaderOptions
                    {
                        ExportIntervalMilliseconds = Convert.ToInt32("10000"),
 };

srikanthccv

otelDeployment:
  config:
    receivers:
      redis:
        endpoint: <redis-host>:6379
    service:
      pipelines:
        metrics/internal:
          receivers: [redis]
          processors: [batch]

srikanthccv

otelDeployment:
  config:
    receivers:
      prometheus:
        config:
          scrape_configs:
          - job_name: pod_metrics
            kubernetes_sd_configs:
            - role: pod
            relabel_configs:

srikanthccv

package main

import (
	"context"
	"fmt"
	"time"

	"github.com/ClickHouse/clickhouse-go/v2"
)

srikanthccv

package main

import (
	"context"
	"errors"
	"math/rand"
	"time"

	"go.opentelemetry.io/otel"
	"go.opentelemetry.io/otel/attribute"

srikanthccv

Morning

1. Warm-up (5 minutes):

   • Begin with a light jog in place or jumping jacks to get your heart rate up.
   • Perform some dynamic stretches to warm up your muscles, focusing on your legs, arms, and shoulders.

2. Circuit 1 (10 minutes):

   • Jump rope for 1 minute at a moderate pace.
   • Immediately perform 10 push-ups.

• Repeat this sequence for a total of 5 rounds.

srikanthccv

                                                        - │ 11887564887837025943 │ 2023-06-26 12:59:00 │ 104381 │ (prev point)
┌──────────fingerprint─┬──────────────────ts─┬──value─┐
│ 11887564887837025943 │ 2023-06-26 13:00:00 │ 104402 │
│ 11887564887837025943 │ 2023-06-26 13:01:00 │ 104461 │
│ 11887564887837025943 │ 2023-06-26 13:02:00 │ 104504 │
│ 11887564887837025943 │ 2023-06-26 13:03:00 │ 104532 │
│ 11887564887837025943 │ 2023-06-26 13:04:00 │ 104590 │
                                                        - │ 12004891769856389124 │ 2023-06-26 12:59:30 │  71476 │ (prev point)

srikanthccv

diff --git a/exporter/opentelemetry-exporter-otlp-proto-common/tests/test_log_encoder.py b/exporter/opentelemetry-exporter-otlp-proto-common/tests/test_log_encoder.py
index c35ced93b..825950a0a 100644
--- a/exporter/opentelemetry-exporter-otlp-proto-common/tests/test_log_encoder.py
+++ b/exporter/opentelemetry-exporter-otlp-proto-common/tests/test_log_encoder.py
@@ -41,6 +41,7 @@ from opentelemetry.proto.resource.v1.resource_pb2 import (
 )
 from opentelemetry.sdk._logs import LogData
 from opentelemetry.sdk._logs import LogRecord as SDKLogRecord
+from opentelemetry.sdk._logs import LogLimits
 from opentelemetry.sdk.resources import Resource as SDKResource

srikanthccv

Why gRPC load balancing is so tricky?

At a high-level, we need to understand two points:

• gRPC is built on HTTP/2, and HTTP/2 is designed to have a single long-lived TCP connection (a sticky and persistent connection);
• To do gRPC load balancing, we need to shift from connection balancing to request balancing;

Some interesting articles about this subject

• Load Balancing gRPC services

srikanthccv

diff --git a/instrumentation/opentelemetry-instrumentation-django/src/opentelemetry/instrumentation/django/__init__.py b/instrumentation/opentelemetry-instrumentation-django/src/opentelemetry/instrumentation/django/__init__.py
index d5e1f072..a03b9c6d 100644
--- a/instrumentation/opentelemetry-instrumentation-django/src/opentelemetry/instrumentation/django/__init__.py
+++ b/instrumentation/opentelemetry-instrumentation-django/src/opentelemetry/instrumentation/django/__init__.py
@@ -90,7 +90,11 @@ from django.conf import settings
 from opentelemetry.instrumentation.django.environment_variables import (
     OTEL_PYTHON_DJANGO_INSTRUMENT,
 )
-from opentelemetry.instrumentation.django.middleware import _DjangoMiddleware
+from opentelemetry.instrumentation.django.middleware import (