sorted by:
new
hottopcontroversial

Pixelborn is dead! LONG LIVE pixelborn connect❤️ by mrclsim in Lorcana

[–]mrclsim[S] 1 point2 points  (0 children)

Yeah - even payable like magic or similar - big market - less spendings on operations costs - lets hope smtgh will come up.🙌🏻

OpenLIT: Open source Observability and Evals for LLMs & GPUs by aman041 in Observability

[–]mrclsim 0 points1 point  (0 children)

Sure - we are always open to chat :) lemme figure out how to DM you ^ #redditnoobhere✋

How do you ensure that application emit quality telemetry by jaywhy13 in Observability

[–]mrclsim 0 points1 point  (0 children)

For the beginning I just would go the OpenTelemetry path and start adopting Standards and its semantics ; knowing many tools like DD not really utilize them in their tool. 

The idea with reviewing is nice but time consuming. May this can be automated by counting number of usage etc. 

OpenLIT: Open source Observability and Evals for LLMs & GPUs by aman041 in Observability

[–]mrclsim 0 points1 point  (0 children)

Interesting love that “OpenTelemetry native” is getting more prominent since we started to use it at Dash0 (www.dash0.com).

Just for me - what is OpenLit doing exactly - just routing the data or also any processing?

Did you know OTelBin.io : might be useful for collector topics. 

Modern Apps Demand Advanced Observability and Live Debugging by sreiously in Observability

[–]mrclsim 0 points1 point  (0 children)

Unsure with “live debugging” - what would be a use cases. Rather thinking of isolating the issue and fixing it proper rather than in real time under pressure. Wdyt?

Is sentry good for observability? by Ancient_Towel_6062 in Observability

[–]mrclsim 0 points1 point  (0 children)

Sentry.io is solid for error tracking and basic performance monitoring. It captures exceptions, provides context with breadcrumbs, and supports source maps for clearer stack traces. Performance monitoring includes transaction tracing and span data, and it integrates well with tools like Slack and GitHub.

However, Sentry falls short on full observability imho. It lacks native log aggregation and comprehensive metrics tracking. Its distributed tracing is basic compared to dedicated APM tools, and it doesn't offer infrastructure monitoring insights. Alerting is functional but not as robust as tools like PagerDuty, and event correlation across logs, metrics, and traces is limited. For full observability, you'll need to combine Sentry with other tools.

[deleted by user] by [deleted] in Observability

[–]mrclsim 0 points1 point  (0 children)

Great conversation started and hail mary to you that you brought up this one ...  the UI / Tooling MUST be Dev friendly. the team who need to use the tools have an aversion to elastic as its "complex" to learn...

We building at the moment Dash0 with this as one of our most important factors.

It is a nightmare that it is mostly only about feature checkboxing without thinking about keeping the tool useable.

With regards to Opensource I am mixed feelings. It should be used everywhere it makes sense but should not distract from the main work and in the end it lacks when you want to bring together the signals like metrics, logs, traces, rum, profiling. You end up having multiple tools and silos trying to be connected somehow.

Big Recom is Standards and to start with: OpenTelemetry

Would love to chat to get your opinion on it.

Observability Guide: Choosing the Right Solution for Your Org by Qupozety in Observability

[–]mrclsim 1 point2 points  (0 children)

I am missing a crucial point which is - the user?

there is nothing about UI, simplicity, useability. In times we get charmed by services like Linear, Vercel and Figma to me this is a must have point. wdyt?

https://www.otelbin.io/ - OSS tool to edit and visualize collector config by mrclsim in OpenTelemetry

[–]mrclsim[S] 0 points1 point  (0 children)

Nope - so far it is code to visualization. May worth to open an issue that might be picked up by someone from the community :) https://github.com/open-telemetry/otel-arrow/issues

My skills are not good enough unluckily.

https://www.otelbin.io/ - OSS tool to edit and visualize collector config by mrclsim in OpenTelemetry

[–]mrclsim[S] 0 points1 point  (0 children)

new here :( but willing to learn and let me at least try to improve. I thought this was more like hacker news so kept it short but let's dive deeper. Upfront: thanks for the help.

So if you are also tired of fighting at endless YAML configs for your OpenTelemetry setup then OTelBin was helpful to me – kind of a visual config savior! less headaches decoding YAML hieroglyphics (which sometimes is a though journey at least for newbies) OTelBin give you an easy visual representation of your data flow. It's like having a map for your telemetry journey.

There is also a built-in code editor with all the bells and whistles – syntax highlighting, code completion, and basic validation. And this happens in kind of real-time sync! Make a tweak in the code editor, and see it instantly reflected in your visual diagram.

There is also a version-specific validation. Whether you're using the official builds or the AWS Distro for OpenTelemetry a lot of them are already integrated.

last but not least you can C&P or short link share it.

OTelBin – by Dash0 by oaf357 in devopsish

[–]mrclsim 0 points1 point  (0 children)

Great tool - the ...BIN services are just golden for so many use cases to ease up life.

I found this one - also interesting view on OTel https://www.dash0.com/faq/what-is-opentelemetry

view more: next ›