How can I improve OpenTelemetry performance without guessing?
A performance change should improve the measured workload without sacrificing correctness or wasting capacity. Which measurements and bottlenecks should be considered first?
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
A performance change should improve the measured workload without sacrificing correctness or wasting capacity. Which measurements and bottlenecks should be considered first?
I'm writing a cloud function in Nodejs (10), and trying to access a secret like so: const [secret] = await new SecretManagerServiceClient().accessSecretVersion({ name: `projects/PROJECT_NUMBER/secrets/SECRET_NAME/versions/latest` }) I created the secret in the web console and the name used in code matches that of the existing secret. On the page for the clou
I'm trying to do the azure service principle password rotation using Terraform, with the latest versions of azuread they have provided this rotation feature, resource "time_rotating" "test" { rotation_years = 5 lifecycle { create_before_destroy = true } } resource "azuread_service_principal_password" "service_principal_password" { service_principal_id = var.
I have a scenario in which I want to have access to resources within one account from another one in AWS (cross-account access) in code. And I want to implement this access using NodeJs, implemented as lambda function and also as a long-running code on EC2. Reading how to do this online, I know I need temporary credentials generated by aws.STS , like this: c
TL:DR - I am trying to deploy my MERN stack application to GCP's Cloud Run. Struggling with what I believe is a port issue. My React application is in a client folder inside of my Node.js application. Here is my one Dockerfile to run both the front-end and back-end: FROM node:13.12.0-alpine WORKDIR /app COPY . ./ # Installing components for be connector RUN
Slightly tearing my hair out with this one... I am trying to run a Docker image on Fargate in a VPC in a Public subnet. When I run this as a Task I get: ResourceInitializationError: unable to pull secrets or registry auth: pull command failed: : signal: killed If I run the Task in a Private subnet, through a NAT, it works. It also works if I run it in a Publ
Based on the docs that I've read, there are 3 methods of patching: patches patchesStrategicMerge patchesJson6902. The difference between patchesStrategicMerge and patchesJson6902 is obvious. patchesStrategicMerge requires a duplicate structure of the kubernetes resource to identify the base resource that is being patched followed by the modified portion of t
I just installed the latest version of Tensorflow via pip install tensorflow and whenever I run a program, I get the log message: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'cudart64_101.dll'; dlerror: cudart64_101.dll not found Is this bad? How do I fix the error?
Configuration must be available to the application without exposing credentials in source control, logs or browser code. What belongs in the runtime and which access controls matter?