51–60 of 83 posts
Earlier quoted context omitted.
Maybe the docs are not good enough for that, but you can just run npx @spotlightjs/spotlight
That’ll get you the sidecar but not the UI widget. I think we could: 1- serve the widget from the sidecar 2- add the CDN distro
Earlier quoted context omitted.
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.
It happens I frequently enough that I forgot it, I've used NextDNS for at least a year, and it's happened at most once before. How often do you try (deliberately) to use something so newly registered? Frankly even most new things have older domains. (I know I'm not alone here in having domains registered for projects that may or may not ever materialise..!) Also maybe worth saying that it's not even really about Next…
Often when myself or one of my friends launches a new web project!
May I suggest adding some additional context to the home page? While I heard about Sentry I find difficult to understand what Spotlight does. I might not be the intended target audience though.
This seems to be a super shared point of view. I’ll admit we were a bit fire-and-forget on the homepage and definitely agree with all the feedback that we need to explain what it is better.
Earlier quoted context omitted.
This seems to be a super shared point of view. I’ll admit we were a bit fire-and-forget on the homepage and definitely agree with all the feedback that we need to explain what it is better.
Is this supposed to be intended for people who are already all-in with Sentry? Or can you possibly share some insight as to where this makes sense to use vs instrumenting with an OTEL SDK?
The other thing to note: OTel doesn’t do everything and Sentrys error context is a big part of the value prop.
Earlier quoted context omitted.
Is this supposed to be intended for people who are already all-in with Sentry? Or can you possibly share some insight as to where this makes sense to use vs instrumenting with an OTEL SDK?
Both. Fwiw lots of folks have yet to invest in OTel so the market is super open. We’re also trying to adjust our approach to leverage OTels community instrumentation when it makes sense. That means that ideally you’ll be able to invest in OTel if you want and we’ll just consume those spans. The other thing to note: OTel doesn’t do everything and Sentrys error context is a big part of the value prop.
This tooling looks really cool and I'd love to play around with it, but am already pretty entrenched into OTel and funneling data through the collector and don't want to introduce too much additional overhead for devs.
[0] https://github.com/open-telemetry/opentelemetry-collector-co...
May I suggest adding some additional context to the home page? While I heard about Sentry I find difficult to understand what Spotlight does. I might not be the intended target audience though.
I also have no idea what it does. "Sentry for development", so it works like sentry but the errors are streamed to localhost??
Earlier quoted context omitted.
Both. Fwiw lots of folks have yet to invest in OTel so the market is super open. We’re also trying to adjust our approach to leverage OTels community instrumentation when it makes sense. That means that ideally you’ll be able to invest in OTel if you want and we’ll just consume those spans. The other thing to note: OTel doesn’t do everything and Sentrys error context is a big part of the value prop.
Thanks for the reply. Would the Spotlight sidecar possibly be able to run independently and consume spans emitted by the Sentry exporter[0] or some other similar flow beyond strictly exporting directly from the Sentry SDK provided by Spotlight? This tooling looks really cool and I'd love to play around with it, but am already pretty entrenched into OTel and funneling data through the collector and don't want to intro…
The idea is that any data source could stream to the sidecar and at the same time consume from it with a curated panel in the UI.
If you’re interested in poking around def hop in our Discord (https://discord.gg/sentry #spotlight) and let us know your thoughts.
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.
A basic README that outlines what it does, how it does it, and basic syntax - this is really easy. Table stakes, I might say. I can checkout your repo and I have everything I need to work
It seems to be getting more and more common to leave your git repository completely undocumented. If you're releasing a software project on github, I want to read about it on github. A basic README that outlines what it does, how it does it, and basic syntax - this is really easy. Table stakes, I might say. I can checkout your repo and I have everything I need to work
We removed bits from the readme as it kept becoming duplicated and eventually wrong. I think that’s the usual reason folks like to avoid it. DRY and all.