Open philn1962 opened 1 year ago
@philn1962 thanks reporting. I think our Engineering Director @danielpaulus actually had the Checkly Agent running in his home lab. Maybe he can chime in.
Awesome! Many of our apps are not "customer facing", so we are dealing with hundreds of W2/1099 employees that are working from home or in remote locations around the country. we use site24x7 for generic "uptime" monitoring but I need more granular data that is specific to frequent callers
Good morning checkly team - any response from Daniel yet?
@philn1962 we just go a Raspberry Pi 3 to start testing this out! We love the use case so we will ping you once we know a little more.
Fantastic! if you need another, I'd be happy to send to you ;-)
Hey @philn1962 , we are currently on our company retreat in Spain so I have little time this week. I can already tell you that ARM64 would most likely work. So if you have RaspberryPi3+ you should be good. For older Raspis you can only use API checks because Playwright does not support Armv7 afaik.
I will take a look next week to see if we can provide a Docker image for you :-)
Have fun with that @danielpaulus! all our RPis are 4Bs with 4GB of RAM so we are good to go
Problem description. What is not working, missing or bugging you? Being able to monitor an application from a private location is a great feature. Unfortunately, it is often not feasible to put a full-blown device in a location simply to run a monitor. Now that many companies are supporting WFH, we no longer have as much control over the environment that an end-user is operating in. Often, we have found that "performance" issues are end-user environmental. Being able to get from "the app performance stinks" to "the end-user is working in a sub-standard environment" can be a difficult hill to climb.
Process description. What step(s) are needed to solve this issue? We would like to be able to send a pre-configure / plug-n-play headless raspberry pi running docker and a synthetic monitoring client to a end-user that frequently reports application performance issues. This will allow us to gather information about the performance specific to their environment. The cost of shipping and potential hardware loss is minimal with a raspberry pi, so if we have to send out a lot of them we won't be badly financially exposed. In order to accomplish this, we need a Checkly Docker container that is built to run on a RPi.
Expected outcome. What should your world (or Checkly) look like after using this function. We expect to be able to quantify performance of our application in any environment as opposed to an enterprise grade network or data center without risking the loss of an expensive piece of hardware.
Thank you! Phil