[HN Gopher] Show HN: SigNoz - open-source alternative to DataDog...
___________________________________________________________________
Show HN: SigNoz - open-source alternative to DataDog, NewRelic
Author : pranay01
Score : 138 points
Date : 2022-10-01 19:00 UTC (3 hours ago)
(HTM) web link (github.com)
(TXT) w3m dump (github.com)
| dominotw wrote:
| good to see solid oss projects coming out of india. I will def
| keep an eye on this one.
| pranay01 wrote:
| thanks. do give it a try and let us know if you have any
| feedback
| pranay01 wrote:
| We just released a major upgrade to SigNoz with support for Logs
| management based on ClickHouse. Would love to get any feedback
| from the community here on what you think and any questions you
| may have for us
|
| Many big companies like Uber and Cloudflare have been shifting to
| ClickHouse as their main workhorse for Logs management seeing
| much better performance. for e.g Cloudflare recently shifted from
| Elastic to ClickHouse and are seeing 8x improvement in memory/cpu
| resource requirement in ingestion.
|
| This is our first release with Logs support and we have added
| support for:
|
| - Filtering logs based on fields
|
| - Full text search in logs
|
| - Live mode to see logs coming in realtime
|
| - Detailed view of logs in table and json format with ability to
| add filters quickly
|
| - Ability to specify interesting fields which will be indexed by
| default
| [deleted]
| gclawes wrote:
| How's this compare to the grafana/prometheus/tempo/loki set of
| tools?
| pranay01 wrote:
| You can find answers to some similar questions here -
| https://signoz.io/docs/faqs/product/#how-is-signoz-different...
|
| Let me know if you have a specific question which is not
| addressed in the above link and will try to answer
| ketzu wrote:
| Is there any introduction to all the services that are included
| in the docker-compose file [1]?
|
| I wanted to give signoz a try, but the sheer amount of services
| attached discouraged me, especially as I have to reconfigure them
| all to work with my setup. (Don't run them directly on the host,
| instead in a separated network, put the network interface behind
| traefik, figure out which access they need, provide all the
| configuration in a nice way without having to clone the full repo
| just to have the configuration files.)
|
| [1]
| https://github.com/SigNoz/signoz/blob/develop/deploy/docker/...
| rad_gruchalski wrote:
| Not associated with the project but a quick look suggests: a
| database (clickhouse), alertmanager, query-service, frontend
| are signoz components, otel* and hotrod are for distributed
| tracing. Otel stands for open telemetry
| (https://opentelemetry.io/), hotrod is a tracing demo app from
| jaeger: https://github.com/jaegertracing/jaeger/tree/main/examp
| les/h....
|
| Without thinking too much about it, I assume that: hotrod is a
| demo data source pushing traces to the otel collector, which
| stores data in clickhouse. Frontend fetches data from
| clickhouse using the query service. Alert manager probably
| looks at traces coming in and detects anomalies, so that you
| can get real-time alerts when things don't look normal.
| ketzu wrote:
| Thank you for the quick explanation, that helps a lot and
| gives me at least a starting point. Although sample services
| surprise me in the suggested docker-compose from the "how to
| install" section.
| pranay01 wrote:
| yeah, it's not ideal - but we kept it to give users who are
| installing for the first time to get a hang of the product
|
| You can easily remove the sample services if you want -
| https://signoz.io/docs/operate/docker-standalone/#remove-
| the...
| pranay01 wrote:
| The comment by rad_gruchalski is mostly accurate
|
| SigNoz has the following components
|
| - Frontend
|
| - ClickHouse (datastore)
|
| - Alert Manager (this is to monitor metrics and create alerts
| which you configure in SigNoz)
|
| - Query Service (which is the backend service which talks to
| datastore & frontend)
|
| - Otel collector ( which the collector provided by
| opentelemetry to collect telemetry data)
|
| The other two components for sample app which can be commented
| out
|
| - Hotrod ( which is a sample app)
|
| - load generator
|
| More details here -
| https://signoz.io/docs/architecture/#architecture-components
| keb_ wrote:
| I used New Relic for the first time at my current job, and while
| service it provides to our team is invaluable, the UI is slow and
| very confusing; I can never remember what button or menu to click
| to get to where I need to go. The fact that it loads so slowly
| just makes it worse.
|
| So I am optimistic for alternative solutions like this!
| jiggawatts wrote:
| At $dayjob the devs use both Azure Application Insights and New
| Relic. Comparing the two, I had the same comments: New Relic is
| appears useful but is too slow in practice. The developers
| generally avoid it in their day-to-day work, which defeats the
| purpose entirely.
|
| We're not in the US, so the cloud-hosted version of New Relic
| is _especially_ slow because of the added latency of the trans-
| oceanic network hop.
|
| For comparison, Azure Application Insights can be deployed in
| our own region. It's not massively faster, but for some UX
| design reason it _feels_ faster and more pleasant to use. It
| might be literally just the network latency, and nothing more,
| but the end result is that it 's used more often.
|
| Application Insights isn't perfect by any means:
|
| - Deployment is a PitA and breaks regularly. The documentation
| related to installing it is confusing, out-of-date, and will
| guide you down dead ends. For example, I got the profiler
| component working _once_ on virtual machines, then it broke,
| and I can 't get it working again for the life of me.
|
| - The underlying Log Analytics workspaces are crazy, _crazy_
| expensive. They 're far more expensive than the competition,
| which then makes high-level services like Sentinel and App
| Insights built on top also too expensive for most orgs. For
| comparison, Log Analytics is about 5x as expensive per GB as
| AWS CloudWatch logs, and up to 30x as expensive as some other
| similar services.
|
| If Microsoft just fixed the installer and used reasonable
| pricing for Log Analytics, the App Insights would be very hard
| to beat, especially for .NET shops.
|
| I'm hoping open-source tools like SigNoz force down the pricing
| from "highway robbery" to merely "greedy".
| pranay01 wrote:
| > so the cloud-hosted version of New Relic is especially slow
| because of the added latency of the trans-oceanic network
| hop.
|
| Curious, does the location of the server introduce the
| latencies (as you mentioned you are not in US)? I would have
| assumed the latency because of server location would be very
| small.
|
| Have you verified that the latency is actually because of the
| trans-oceanic network hop?
| jiggawatts wrote:
| At least a hundred milliseconds of _additional_ latency is
| unavoidable across any ocean crossing. It's just physics.
|
| All US-hosted web services feel slow here. It's a baseline
| sluggishness that permeates everything we use that is cloud
| hosted.
|
| The only exception is services that have local instances or
| replicas of some sort.
| pranay01 wrote:
| I see, very interesting.
|
| Is this latency deterring enough that you prefer running
| things in your region and not prefer SaaS product which
| are generally hosted in US/EU? Or is this just a
| discomfort which you deal with
| dijit wrote:
| Consider that each connection is a round trip (IE; hundred+
| ms latency is multiplied by 3 due to handshakes being
| 3-stage.).
|
| Consider that every fetch of a resource may itself include
| another resource (IE; a html page which contains a CSS
| include).
|
| Now consider that this happens recursively (IE from the
| above example: a CSS include that itself includes a font or
| an image).
|
| It's very easy to get 1+s load times with transatlantic
| latency alone.
| pranay01 wrote:
| thanks for sharing, I never thought this could be an
| issue
|
| Question: Does this increase in latency make cloud
| services less interesting for companies which are not in
| US? What kind of cloud services will be especially
| affected
| dijit wrote:
| Cloud services usually have global availability, you
| choose where you host.
|
| A lot of people in Europe are using European datacenters.
|
| That is not to say there's no issues: The consoles can be
| unbearably slow at times. (Google Cloud being probably
| the worst offender in my experience, despite being a fan
| otherwise).
|
| Amazon supports consoles in other regions, but if you use
| `console.aws.amazon.com` then it is us-east; it doesn't
| automatically change it for you.
|
| Here's the list:
| https://docs.aws.amazon.com/general/latest/gr/mgmt-
| console.h...
|
| Regarding making Cloud less interesting:
|
| Europe basically follows whatever SV is doing, to make a
| crass comment: an article could be produced from SV
| saying eating poop would make better engineering and
| European "tech" companies would assuredly start buying up
| the sewage systems.
|
| Even when it doesn't make sense; we seem to follow.
| capableweb wrote:
| After using AWS for more than 10 years in various
| capacities, I've never seen that the console is available
| in multiple regions! Sometimes it is dog slow for me when
| I'm in a various different geographic locations, I hope
| this newly learned fact will make my experience slightly
| better in the future, thanks for sharing that!
|
| It does make me wonder though, why not automatically
| redirect people to the console that is closest to them?
| They could done anything from Anycast DNS to showing a
| simple little notification showing people there was an
| alternative possibly closer to them when logging in, but
| as far as I know, nothing is done about this.
| pranay01 wrote:
| thanks for the kind words. To give it a try and let us know if
| you have any feedback/questions.
|
| We also have an active slack community if you have any
| questions on how to set up or have an feedback for us -
| https://signoz.io/slack
| reilly3000 wrote:
| I just learned about SigNoz. I spend a lot of time flipping
| between New Relic and Splunk, and my company spends a ton on
| both. I'm interested to hear from users and learn if it's prod
| ready as a New Relic alternative. I'm especially interested in
| something that could run locally so I can profile using the same
| tools that run in prod. Any feedback?
| jakswa wrote:
| Goodness I hope this is good because I will make my company
| gobble it upppp if so.
| pranay01 wrote:
| feel free to test it out. We have an active slack community as
| well if you have any questions on how to setup etc.
| https://signoz.io/slack
| saintfiends wrote:
| We thought so too until we found out it doesn't support any
| kind of SSO
|
| https://github.com/SigNoz/signoz/issues/1188
| bogota wrote:
| I mean if that is the single thing stopping your company from
| using it then just add support for it. The cost of DD monthly
| bill more than supports spending a week or less it would take
| to add
| rad_gruchalski wrote:
| That or just put the frontend behind a reverse proxy with
| sso.
___________________________________________________________________
(page generated 2022-10-01 23:00 UTC)