Steve Christensen

Another option could be the Secrets Store CSI driver -- https://github.com/kubernetes-sigs/secrets-store-csi-driver -- it has plugins for Vault, and various cloud provider's secret stores (AWS, GCP, Azure).

moved SWN & Fouth Page into app for 1.0 moved SGNP generators to gh-86

@cromlyngames Thanks, Patrick! Those look great!

also look at https://www.reddit.com/r/DnDBehindTheScreen/comments/5df57w/cavern_building_a_primer/ or split that and https://www.reddit.com/r/TalesFromDrexlor/comments/4b6p2m/the_complete_hippo/ into separate supplement https://www.reddit.com/r/DnDBehindTheScreen/comments/5p1hy0/tables_to_turn_20_classic_enemies_into_nuanced/

need to remove that APK version from the github releases -- the release build is broken. Caught it before it rolled out to the beta/release channel on Google Play, but...

having the same issue in a GKE cluster -- 403 on trying to hit the k8s API for namespaces. RBAC looks right to me. also tried getting onto the pod...

version 1.20.0 of the otel semconv was `http.server.duration` the latest semconv standard (1.22) now recommends `http.server.request.duration` https://github.com/open-telemetry/semantic-conventions/blob/main/docs/http/http-metrics.md you could look at OTEL_SEMCONV_STABILITY_OPT_IN to decide which metrics to create, as described...

I'm seeing what might a similar issue -- intermittently an incorrect binding is injected into a resource. (generally, I have to restart my application to get different behavior) I'm trying...

is there already a ticket for correcting the units in the hikaricp instrumentation? in the current agent (2.13.1), hikaricp instrumentation for db.client.connections.{create_time,wait_time,use_time) implements the 1.24.0 semconv and units are 'ms'...

There's also a `thread.name` on the `jvm.cpu.longlock` metric. But, I didn't see that causing a cardinality problem in these applications.