If you've tried to get started with @grafana Loki, there's a little thing you'll have to contend with first... LogQL. Here's what LogQL is, how to ease into using it, and how to write your first queries in it. https://youtu.be/57dQwcmqkpQ
#observability #grafana #loki
Recherches récentes
Options de recherche
#observability
0 message0 participant0 message aujourd’hui
New Open-Source Tool Spotlight 
Kubernetes History Inspector (KHI) is an agentless log viewer built for visualizing Kubernetes audit logs. Its timeline-based log analysis and resource relationship diagrams simplify cluster troubleshooting—no complex setups or commands required. #Kubernetes #Observability
Project link on #GitHub 
https://github.com/GoogleCloudPlatform/khi
#Infosec #Cybersecurity #Software #Technology #News #CTF #Cybersecuritycareer #hacking #redteam #blueteam #purpleteam #tips #opensource #cloudsecurity
— 
P.S. Found this helpful? Tap Follow for more cybersecurity tips and insights! I share weekly content for professionals and people who want to get into cyber. Happy hacking 
We want to hear from you! What SHOULD #PostgreSQL stats look like in the future? What do you think? Is StatsMgr on the right path, and what else can we be doing?
Let us know in the comments below, or reach out to the team - we want to know how best StatsMgr can be useful for #Postgres users, everywhere!
The new #observability as code features and tools in #Grafana 12 allow you to version, validate, and deploy dashboards like any other code base in your organization, reducing manual processes and increasing consistency across your team.
https://grafana.com/blog/2025/05/07/observability-as-code-grafana-12/?camp=blog&mdm=social
Grafana LabsObservability as code: automate observability workflows and manage dashboards as code in Grafana | Grafana LabsThe new observability as code features and tools in Grafana 12 allow you to version, validate, and deploy dashboards like any other code base in your organizations, reducing manual processes and increasing consistency across your team.
Is Node.js the future of backend development, or just a beautifully wrapped grenade?
Lately, I see more and more backend systems, yes, even monoliths, built entirely in Node.js, sometimes with server-side rendering layered on top. These are not toy projects. These are services touching sensitive PII data, sometimes in regulated industries.
When I first used Node.js years ago, I remember:
• Security concepts were… let’s say aspirational.
• Licensing hell due to questionable npm dependencies.
• Tests were flaky, with mocking turning into dark rituals.
• Behavior of libraries changed weekly like socks, but more dangerous.
• Internet required to run a “local” build. How comforting.
Even with TypeScript, it all melts back into JavaScript at runtime, a language so flexible it can hang itself.
Sure, SSR and monoliths can simplify architecture. But they also widen the attack surface, especially when:
• The backend is non-compiled.
• Every endpoint is a potential open door.
• The system needs Node + a fleet of dependencies + a container + prayer just to run.
Compare that to a compiled, stateless binary that:
• Runs in a scratch container.
• Requires zero runtime dependencies.
• Has encryption at rest, in transit, and ideally per-user.
• Can be observed, scaled, audited, stateless and destroyed with precision.
I’ve shipped frontends that are static, CDN-delivered, secure by design, and light enough to fit on a floppy disk. By running them with Node, I’m loading gigabytes of unknown tooling to render “Hello, user”.
So I wonder:
Is this the future? Or am I just… old?
Are we replacing mature, scalable architectures with serverless spaghetti and 12-factor mayhem because “it works on Vercel”?
Tell me how you build secure, observable, compliant systems in Node.js.
Genuinely curious.
Mildly terrified and maybe old.
Come diceva quel vecchio slogan, “la potenza è nulla senza il controllo”. 
Il 23 maggio alla #conferenza #ITDevCon 2025 Spring Edition parleremo di #observability introducendo #Prometheus e il suo client per #Delphi. Vedremo come integrare #metriche, creare #alert, in generale come ottenere una visione chiara di come si stanno comportando applicazioni e servizi in produzione. 
Uno sguardo veloce alla parte teorica, con esempi e consigli pratici. 
Biglietti e info: https://itdevcon.it/home/spring-edition-2025/
What’s Really Going On in Your Quarkus App? A Java Developer’s Guide to Jolokia and Hawtio
https://myfear.substack.com/p/whats-really-going-on-in-your-quarkus
#Java #Quarkus #Observability #Micrometer
Save the date! After #GrafanaCON Day 1, join Embrace, Tailscale & Grafana for happy hour at SPIN Seattle!
Drinks, bites & ping pong — May 6, 4–6 PM.
Space is limited — RSVP now!
Through standardized tagging and a migration to #Grafana Cloud, the SpotOn engineering team completely transformed its #observability strategy, ditching complexity for control. Here's a closer look.
Grafana LabsHow SpotOn overhauled its observability strategy with standardized tagging and Grafana Cloud | Grafana LabsThrough standardized tagging and a migration to Grafana Cloud, the SpotOn engineering team transformed its observability strategy, ditching complexity for control.
Vector 0.46.0 now includes a #Postgres sink!
It's time to send my logs to TimescaleDB 
vector.devVector v0.46.0 release notes
Simplify debugging with Deno and @opentelemetry 
logs associated with requests immediate traces and metrics works on Node.js backends
without any additional code or config
https://deno.com/blog/zero-config-debugging-deno-opentelemetry
It's the 2025 Observability Survey Wrapped!
See the 
to preview what 1,255 #observability experts are saying about traces, observability costs, open source, Prometheus vs. OTel, observability challenges, and more.
For even more insights, check out the full report (no email required): https://grafana.com/observability-survey/?mdm=social&src=masto
Man Prometheus is a pain to recover once its data store is in any way out of shape. Did NOT help that it was buried inside Kubernetes inside a PVC.
Thankfully it was only Dev environment today but if this ever pages on Prod we're losing data as it stands.
I'll write something up for a run book but eesh.
Is #OTel the Last #Observability Agent You’ll Ever Install?
https://thenewstack.io/is-otel-the-last-observability-agent-youll-ever-install/
The New Stack · Is OTel the Last Observability Agent You’ll Ever Install?The open source OpenTelemetry Collector has dramatically challenged the dynamics between observability vendors and end users.
As your #Shopify site scales and grows, you’ll need deeper insights into performance and the overall end-user experience.
Here’s how to get that visibility (and more) in #Grafana Cloud Frontend #Observability. https://grafana.com/blog/2025/03/04/how-to-monitor-your-shopify-store-with-grafana-cloud-frontend-observability/?camp=blog&mdm=social&src=masto
Grafana LabsHow to monitor your Shopify store with Grafana Cloud Frontend Observability | Grafana LabsAs your Shopify site scales and grows, you’ll need deeper insights into performance and the overall end-user experience. Here’s how to get that visibility (and more) in Grafana Cloud Frontend Observability.
A répondu dans un fil de discussion
I'm going to talk about #Observability, notably around #Otel and #Honeycomb, as I feel these things aren't shouted about enough, and how much of a massive game changer they can be with regards to writing and observing software.
Any #php recommendations for #observability approaches if you want to hook into an existing long running php process?
Something like strace, but which looks more nicely
#Traefik v3.3 - codename "Saint-Nectaire" - is here!
This release focuses on 2 critical areas: Observability capabilities Improved documentation structure
These upgrades make Traefik v3.3 even more powerful for platform engineers tackling complex cloud-native environments.
Learn more: https://bit.ly/4i7nRt3
Nice - #Quarkus has an official page in the #OpenTelemetry docs now - https://opentelemetry.io/docs/zero-code/java/quarkus/ #java #observability
OpenTelemetryQuarkus instrumentationQuarkus is an open source framework designed to help software developers build efficient cloud native applications both with JVM and Quarkus native image applications.
Quarkus uses extensions to provide optimized support for a wide range of libraries. The Quarkus OpenTelemetry extension provides:
Out of the box instrumentation OpenTelemetry SDK autoconfiguration, supporting almost all system properties defined for the OpenTelemetry SDK Vert.x based OTLP exporter The same instrumentations can be used with native image applications, which are not supported by the OpenTelemetry Java agent. Note Quarkus OpenTelemetry instrumentation is maintained and supported by Quarkus. For details, see Quarkus community support.