When I was setting up Honeycomb with my Lambda functions there was something that bothered me: the OpenTelemetry config file contained my API keys and environment-specific details. I needed to keep my bundle environment-agnostic, and I really didn’t want to be committing API keys to version control. You can read more about the adventure itself in my other post, or continue reading this post for my solution.
Read more »This is a condensed guide to how I configured AWS Lambda to work with Honeycomb and OpenTelemetry.
Read more »I have several existing Lambda functions which are all built on Node.js which I wanted to connect to Honeycomb. I spent some time over the weekend working through it, and this is my stream-of-consciousness.
Read more »Read more »Also known as: how to move hundreds of files in S3 that you accidentally put in the wrong place because you misconfigured a Kinesis Firehose.
Post http://kapacitor.default:9092/write?consistency=&db=telegraf&precision=ns&rp=autogen: dial tcp: lookup kapacitor.default on 100.1.1.1:53: no such host service=subscriber
If you’re seeing something like this error in your InfluxDB logs, and don’t know what it means: Kapacitor has created one or more subscriptions in your InfluxDB database, and InfluxDB is trying to POST to the Kapacitor endpoint; however, Kapacitor is unreachable. Kapacitor might be unreachable because it’s down, or you have a network partition or other connectivity issue, or in my case you’ve actually just destroyed your Kapacitor instance.
Read more »