I am happy to announce that version 4.11.0 of #syslog_ng is now available. The main attraction is the brand new #Kafka source, but there are many other smaller features and improvements, from syslog-ng contributors around the World.
https://www.syslog-ng.com/community/b/blog/posts/version-4-11-0-of-syslog-ng-is-now-available
#elasticsearch #macos #opensearch
I am happy to announce that version 4.11.0 of #syslog_ng is now available. The main attraction is the brand new #Kafka source, but there are many other smaller features and improvements, from syslog-ng contributors around the World.
https://www.syslog-ng.com/community/b/blog/posts/version-4-11-0-of-syslog-ng-is-now-available
#elasticsearch #macos #opensearch
Da hat sich jemand bei #LinkedIn "identifizieren" lassen um das nette blauen Häckchen zu bekommen.
Was das mit #Anthropic, #OpenAI, #GrowCloud, #AWS, #GCP, #ResistantAI, #FingerprintJS, #Mongodb, #Snowflake, #Elasticsearch, #Confluent, #DBT, #SigmaComputing, #Tableau, #Stripe und #Twillo zu tun hat?
"I handed a US company my #passport, my #face, and the mathematical geometry of my skull. They cross-referenced me against credit agencies and government databases. They’ll use my #documents to train their AI. And if the US government comes knocking, they’ll hand it all over — even if it’s stored in #Europe, even if I’m European, and possibly without ever telling me."
#privacy #nightmare #gdpr #dsgvo
https://thelocalstack.eu/posts/linkedin-identity-verification-privacy/
Da hat sich jemand bei #LinkedIn "identifizieren" lassen um das nette blauen Häckchen zu bekommen.
Was das mit #Anthropic, #OpenAI, #GrowCloud, #AWS, #GCP, #ResistantAI, #FingerprintJS, #Mongodb, #Snowflake, #Elasticsearch, #Confluent, #DBT, #SigmaComputing, #Tableau, #Stripe und #Twillo zu tun hat?
"I handed a US company my #passport, my #face, and the mathematical geometry of my skull. They cross-referenced me against credit agencies and government databases. They’ll use my #documents to train their AI. And if the US government comes knocking, they’ll hand it all over — even if it’s stored in #Europe, even if I’m European, and possibly without ever telling me."
#privacy #nightmare #gdpr #dsgvo
https://thelocalstack.eu/posts/linkedin-identity-verification-privacy/
And we'll see here in a minute if I've just borked my instance...
Upgraded elasticsearch to 9.X and node.js to 22... and rebuilding...
If this instance goes splort, at least I'll have something to do this weekend.
Elasticsearch Was Never a Database
https://www.paradedb.com/blog/elasticsearch-was-never-a-database
#HackerNews #Elasticsearch #Database #Discussion #Technology #Insights #DataManagement
📊 #VictoriaLogs - Fast #opensource log database from #VictoriaMetrics using 30x less RAM & 15x less disk than #Elasticsearch and #Loki. Handles terabytes of logs efficiently with the powerful #LogsQL query language. Available in single-node and cluster mode. #observability #devops #logging
🧵 👇
📊 #VictoriaLogs - Fast #opensource log database from #VictoriaMetrics using 30x less RAM & 15x less disk than #Elasticsearch and #Loki. Handles terabytes of logs efficiently with the powerful #LogsQL query language. Available in single-node and cluster mode. #observability #devops #logging
🧵 👇
Marmot – Single-binary data catalog (no Kafka, no Elasticsearch)
https://github.com/marmotdata/marmot
#HackerNews #Marmot #Data #Catalog #Single #Binary #Kafka #Elasticsearch #Open #Source
Mastodon admins running a public server,
If you have elasticsearch-powered advanced search options it might be worth mentioning this on your server's About page.
Some people want to know if this feature is present when considering servers to move to, and as far as I know there's no way to tell without joining? (Or is there?)
Não há muitas instâncias Mastodon a usar #elasticsearch pois não? De que recursos necessários estamos a falar?
#ciberlandia @sysop
... or maybe can someone explain to me the difference between #elasticsearch apm and esc? Are they 2 completely separate systems or can I use apm to generate ESC logs?
Yeah now I've a purely #elasticsearch #esc issue, When I try to send a new event the call fails with a 500 and cryptic error, and google is not helpful...
STATUS: 500, BODY: {
"error": {
"reason": "[_data_stream_timestamp] meta field has been disabled",
"root_cause": [
{
"reason": "[_data_stream_timestamp] meta field has been disabled",
"type": "illegal_state_exception"
}
],
"type": "illegal_state_exception"
},
"status": 500
}
Hey rustaceans, I need to plug my #axum server which uses the tracing crate for logs to our elasticsearch logging service, which uses ESC I believe?
It seems there's no off the shelf tracing_layer to talk to elasticsearch , and trying to write my own I'm running in the issue of needing to use an async method to send the message from a sync context (on_event() of tracing::Layer). Anything I've missed to make my live easier? #rustlang #tokio #elasticsearch
... or maybe can someone explain to me the difference between #elasticsearch apm and esc? Are they 2 completely separate systems or can I use apm to generate ESC logs?
Hey rustaceans, I need to plug my #axum server which uses the tracing crate for logs to our elasticsearch logging service, which uses ESC I believe?
It seems there's no off the shelf tracing_layer to talk to elasticsearch , and trying to write my own I'm running in the issue of needing to use an async method to send the message from a sync context (on_event() of tracing::Layer). Anything I've missed to make my live easier? #rustlang #tokio #elasticsearch