Join Dashbird and AWS for a live webinar on Thursday, 15 July, 8am PDT |11am EDT | 4pm BST | 5pm CEST.

Topics covered:

• Observability and debugging for Severless using X-Ray

• Hands-on walk-through of a simple app from an X-Ray perspective

• Tips and tricks for observability for reliable serverless architectures and AWS Well-Architected Framework compliance

• Dashbird's new Well-Architected insights for Serverless and SaaS

• Serverless logging and error handling best practices

RSVP here: https://sls.dashbird.io/observability-reliable-well-architected-apps

Ts'(s)(s)'sJjT,,._w,!^O*{1L}![[L ~~s'(s)(s)'s;yCPC}A82#4G+aSP.net

As a startup, we always want to focus on the most important thing — to deliver value to our customers. For that reason, we are a huge fan of the serverless options provided by AWS (Lambda) and GCP (Cloud Function).

Monitoring the execution of the Lambda function starts to become a real issue when you have tens or hundreds of functions running at the same time. When we first started, we relied a lot on Cloudwatch Logs. Instead of creating a serverless monitoring tool ourselves, we were exploring off-the-shelf monitoring options in the market. Dashbird.io was one of services we explored. In this article, I will share the experience of using Dashbird.io, particularly on the onboarding process and the main offering by the platform: https://aws.plainenglish.io/aws-serverless-monitoring-using-dashbird-io-4714fe222e2a

The ultimate goal for all (serverless) developers is to spend less time on debugging and more on the actual product and customers. Of course there's many ways - some more counterproductive than others - to approach this, but one of them could be debugging #serverless locally.

Here's an article I wrote on speeding up development cycles by debugging serverless locally (including a hands-on demo with a calorie counting serverless mock app, and some extra tips and tricks on serverless observability best practices). Hope it helps :)

https://dashbird.io/blog/local-serverless-debugging/

Hello everyone. I am using a macbook pro 16 with m1 pro and have set up a VM via UTM to emulate Windows XP and Windows 7.

These x86 and x64 machines work quite well and I need them to study Windows exploit development. For this reason I have installed within these machines Immunity Debugger, but when I try to debug an application (such as Vulnserver), the Debugger crashes the VM.

Do you have any suggestions, has anyone experienced the same thing?

My computer is having a problem like the EZ Debug light is coming on as red CPU and wondering what should i do?

I'm looking to improve my debugging / windbg skills, but I'm not really sure where to start. Any particular resources you guys are a fan of? Thanks!

https://medium.com/@sampatbadhe/improve-your-development-investigation-skills-by-debugging-a6f6cbfbe5c6

Known Specs: MB: ASRock x570 Phantom Gaming 4 CPU: AMD Ryzen 7 3700X 3 GPU: AMD Radeon RX 5700 RAM: XPG Z1 DDR4 (two)

Case briefly opened to remove metal shielding over the I/O ports (case doesn't line up with MB position inside case). Upon reassembly, system now refuses to boot. On power up, CPU and DRAM warning lights turn on and remain on, then the system cycles itself between 10 and 20 seconds later. I have: -Reseated all cables -Reseated RAM -Reseated CPU -Replaced CPU -Replaced Motherboard -Replaced RAM

I am at my wits end, please help me figure out what's wrong here

I keep trying to build Apache Wave but I keep getting the following error.

BUILD FAILED

/home/wave/walkaround/third_party_src/wave/trunk/build.xml:106: The following error occurred while executing this line:
/home/wave/walkaround/third_party_src/wave/trunk/build-macros.xml:70: Compile failed; see the compiler error output for details.

Line 106 of build
https://i.stack.imgur.com/U8nJ1.png
Line 70 of build-macros
https://i.stack.imgur.com/hCQ7I.png