Live data from Hacker News

Spotlight: Sentry for Development

spotlightjs.com

31–40 of 83 posts

Re: Spotlight: Sentry for Development

#31

Sorry, what does this do exactly? I have only cursory familiarity with Sentry and it's not obvious why would I want it.

It basically leverages the Sentry SDKs during development and sends them into a local UI rather than a production Sentry instance. It also shows the data in a way that's more akin to local development.

Re: Spotlight: Sentry for Development

#32

Sorry, what does this do exactly? I have only cursory familiarity with Sentry and it's not obvious why would I want it.

“What sql queries did the api make that my react ui is talking to”

Makes it much easier to debug local systems during development.

Same kind of thing for errors- takes something that shows up in a console somewhere and brings it into a UI.

Re: Spotlight: Sentry for Development

#33
post #2

David from Sentry here. If yall have feedback around Spotlight we’d love to hear it. This is a passion project for a few of us and seemed like a natural fit for our technology, and becomes especially interesting with the service oriented world we all find ourselves in.

I'd love to see this a replacement for django debug toolbar in future :D

Re: Spotlight: Sentry for Development

#34
post #2

David from Sentry here. If yall have feedback around Spotlight we’d love to hear it. This is a passion project for a few of us and seemed like a natural fit for our technology, and becomes especially interesting with the service oriented world we all find ourselves in.

I'm curious. I figure you considered building the UI as a DevTools extension; why 'd you go this in-page-DOM-overlay route instead?

Re: Spotlight: Sentry for Development

#36
post #14
post #12

Earlier quoted context omitted.

Both say 'Unable to connect' for me (Firefox built in page) in the UK. Which I think means the name resolved but no response. (But I'm on mobile so can't say more than that.)

The domain name is new, and those get blocked by many DNS-based ad-blocks. I use NextDNS and get the same error - spotlightjs.com is blocked (resolves to 0.0.0.0) NextDNS calls this "Block Newly Registered Domains (NRDs)", and applies to all domains <30 days. ZScaler has something similar for corporate users, so people connecting from work might see a big red warning page.

Isn't a tool that blocks all domains registered less than 30 days ago hugely annoying?

I guess I can see the upside in terms of helping avoid newly registered phishing sites, but I don't think I could live with the downsides.

Re: Spotlight: Sentry for Development

#38
Feature request: documentation for running this with a Python web app. It looks to me like it should work - the Python Sentry library can presumably publish to the local Spotlight forwarder.

I don't have a npm/npx/etc build mechanism setup, so I'd appreciate instructions for running a separate web server to serve the UI, rather than running the UI integrated directly into my existing Python web application.

Re: Spotlight: Sentry for Development

#39
post #38

Feature request: documentation for running this with a Python web app. It looks to me like it should work - the Python Sentry library can presumably publish to the local Spotlight forwarder. I don't have a npm/npx/etc build mechanism setup, so I'd appreciate instructions for running a separate web server to serve the UI, rather than running the UI integrated directly into my existing Python web application.

Would a bundled JS asset work for the UI? Eg something from a CDN?

Feel free to add a GitHub issue with more details if that’s easier!

Re: Spotlight: Sentry for Development

#40
post #2

David from Sentry here. If yall have feedback around Spotlight we’d love to hear it. This is a passion project for a few of us and seemed like a natural fit for our technology, and becomes especially interesting with the service oriented world we all find ourselves in.

I'm curious. I figure you considered building the UI as a DevTools extension; why 'd you go this in-page-DOM-overlay route instead?

More control and far lower barrier to hack on. This actually opens up a lot of doors for us even if you ignore usability and discoverability. For example, we have a POC that pops the overlay when a server error happens, giving you a rich debug experience where otherwise you might not be able to have one.
Post reply on HN