Got a question about QueuePeek, found a bug, or want to talk about a feature? Send a message — the inbox is mine, not a support queue. I reply to everything.
Start with the basics: the connection string or access key is correct, the resource exists in the namespace/account you're pointing at, and your machine can reach the endpoint (no VPN or firewall blocking outbound to :443).
For Azure Service Bus with Entra ID auth: make sure your account has the Azure Service Bus Data Receiver role at minimum. For AWS SQS: the IAM principal needs sqs:ReceiveMessage, sqs:GetQueueAttributes, and (for management) sqs:ListQueues.
Absolutely — that's the most useful kind of message you can send. RabbitMQ and Kafka are already on the shortlist; other brokers are weighted by how many people ask. Tell us which broker, which version, and what you'd use it for.
Not publicly, yet. If you're piloting QueuePeek inside a team and want a heads-up on what's coming in v1.x, get in touch and we'll share what's planned.
Occasionally, yes — but it's not the main focus of DS Tech Works. If you have a specific project in mind, send a note and we'll see if there's a good fit.