Start learning this lesson now

Programming, Centralized Logging Solution for Google Cloud Platform (Cloud Next '18... (3)

Centralized Logging Solution for Google Cloud Platform (Cloud Next '18... (3)

because we need to create or try to gather some context

and what we refer with context, because your application is

running in a pod.

That pod has a name.

That pod has an ID, an identification.

Also, you're running in a namespace.

If you deploy a pod, that pod belongs to a namespace.

It's running in a node, in a host.

Maybe you added some labels and annotation to the pod,

because maybe an annotation say, no--

this-- for example--

sorry.

Some labels saying, OK, [INAUDIBLE]

running or belongs to production, quality, testing,

or anything like that.

So how do you create all this context

for an application which is running in Kubernetes?

This whole context also [INAUDIBLE] more complexity.

And it's because this.

Because the container name and the container ID,

you can find it in the file system.

And I'm talking here about the very low level

how things operate.

You can get that.

But all of the other components come from the Kubernetes API

server or the master server.

So you have some information that is locally

in the node and other information that's

in a separate machine.

And you need that your logging agent

be able to get all of this information together.

And that's why the logging agent that you use and that

Stackdriver use needs to be able to handle all of this for you,

because of course, you cannot do this manually.

But your logging agent needs to be able to create a file

system, understand the messages, parse the messages--

which are in different formats--

and correlate all the information together

with context coming from the API server.

And that's Fluentd.

Actually, Stackdriver uses Fluentd.

You will find it as Google Fluentd,

because it's a Fluentd package that's

ready to use with Google services, which

has the whole extensions and integration

with the Stackdriver right out of the box.

And once you get the things of Fluent as a log processor,

you can send things to Stackdriver or maybe

your own database.

Maybe you're running on prem, or you have your own system

to store logs.

So that's why the logging agents--

it's not easy to be a logging agent as a tool,

and also needs to be able and communicate

with different components over the network.

Now log processing in Kubernetes is like the next step.

If we think that we have just a single node,

well, we'll have the master and a single node.

Fluentd, as a logging agent, needs to run as a DaemonSet.

Do you know what a DaemonSet is?

Are you familiar with pods?

We just spoke about.

OK.

A DaemonSet-- it's like a pod, but this pod

runs on every node of the cluster.

So if you append more nodes to your Kubernetes cluster,

like a [INAUDIBLE] machine, and you already deploy it,

a DaemonSet, you're going to get a new pod with that DaemonSet

running on that new node.

So the way to work is that you deploy Fluentd as a DaemonSet.

Of course, [INAUDIBLE] is already

working by default. What it does, it's running,

and it starts reading the whole log files that we explained

a few slides ago, and all the content and JSON

files that were created.

Once it read the whole content from the application,

it makes sure to gather the metadata that

agitate every message, with every container,

with every port, with labels, annotations, and so on.

So the simple message that we started at the beginning

becomes something like this with context.

Because it has Kubernetes, it has a host, pod name, pod ID,

container, name, namespace, and so on,

because then in a Stackdriver or any database that you're using,

you don't want to query a show me the message that start

with "Hey Next."

You want to say, show me all the messages that,

for example, that the container name, so

Kubernetes, that container name, equal "next."

So this metadata allows you to do a better data analysis

and help the storage solution to create the data that you really

care about it and not query all of them.

MARY KOES: Thanks.

So I mentioned earlier that we have the same team that

supports both our Cloud Logging solution and Google's

internal logging solution.

So we've learned a lot of lessons

talking to customers like yourselves and customers

at Google--

who use the logging tools that we build.

So I wanted to share some lessons learned.

One is the value of structured logs,

so not all logs are created equal.

They all have great potential, but if we format them

in a specific way, we're able to answer questions more easily.

So an unstructured log might have

a text payload of blah, blah, blah, purchased four widgets.

A structured log will have a lot of key value

pairs in JSON format.

This makes it much easier, then, to answer questions like,

how many unique customers purchased a widget?

How many widgets were purchased overall?

If you use structured logs, you can then send--

when you, for example, send stuff to BigQuery,

that structure will persist and make

it much easier to interact with your logs downstream as well.

Plus, you can do things in Stackdriver logging like say,

show me the customer ID hash.

I want that to be displayed easily,

so I can understand what's going on more quickly.

The other tip that we have learned over the years

is that it can be really tricky to get

the right level of logging.

If you do too much, it's crazy expensive,

and you can't find anything in your logs.

If you do too little, then you don't have the data

that you need when you need it.

And so trying to get that just right level of logs

can be a real challenge both internal to Google

and for our customers.

There's no magic bullet here, but one thing

we found to be really helpful is to enforce

a consistent definition for logging levels

through your code.

So an error should be something that really stopped your code,

and you expect somebody to actually investigate here,

whereas maybe debug and info are less important.

And that makes it easier, when I filter,

to quickly find the information that we care about.

And the final kind of insight we've derived over time

is that it's really helpful to have data about the log volume

so that you can iterate and refine this over time.

So specifically, in Stackdriver Logging,

we have metrics at a very fine-grained level,

so you can see not only which resources are sending logs,

but which logs or which--

are you getting mostly errors, or are these mostly info

statements?

And you can slice and dice your data

in all sorts of ways, which can allow

you to iterate on your logging solution over time.

EDUARDO SILVA: So getting back to logging agents,

there are many solutions and open source products available.

But when talking specifically about Fluentd,

which is the default agent in Stackdriver and also

for [INAUDIBLE] companies and products,

we can think that Fluentd is more than just

a simple open source project.

I would like to say that it is a whole ecosystem.

Since the moment there are many companies contributing back

to the same project means that it's

more relevant for the market, and also, it's

becoming a huge solution.

And at some point, people said that Fluentd for some cases

was too heavy, or we have some performance issues.

And sometimes the question is, how many records are you

ingesting per second?

Sometimes they say, a few thousands per second.

Of course, you're going to have some performance penalties.

You need memory, CPU, and you are filtering data,

and you have like 10 filters, that is time-consuming.

And they said, OK, but we need something lightweight.

Fluentd original is written in Ruby and C.

It's quite performant, but at high scales,

some companies and user customers

said we need something that can be lightweight and more

tied to cloud native solutions.

And that's why we created a second project, which

is called Fluentbit, created same by Treasure Data, now

driven by the community.

It's also with the Cloud Native Computing Foundation,

and Fluentbit tried to solve the problems in the cloud native

space in a different way.

You've seen the same background or experience from Fluentd.

This is not like a replacement for Fluentd,

but most of cases, people said, I want to use Fluentd.

And for this special namespace class,

I'm going to run Fluentbit because of performance

reason or special features.

The good thing about Fluentbit is that it's

written in Perl and C language.

It's optimized for performance, low memory footprint.

And it also has a pluggable architecture.

It's pretty much a Fluentd, but Fluentd ecosystem

is quite huge.

We have 700 plug-ins.

Here, we have like 45.

So you can see that it's more tied for specific things,

and it's fully integrated with Kubernetes and Prometheus,

and it's a sub-project of the CNCF.

And like a kind of announcement, we

are releasing in a couple of days the new version, which

is called 0.14.

I think that sometimes numbers does not mean something.

The [INAUDIBLE] been around for more than three years,

but we're trying to have the 1.0 at the end of the year.

And 0.14 will have integration with Google Stackdriver.

It will not, at the beginning, this integration

is quite experimental.

It means that it doesn't have the whole features

that Google Fluentd has, but we're working on that.

Also, we will have the load balancing capabilities.

In logging, there is one specific feature

that if you are dispatching your logs to your service,

and you have some [INAUDIBLE] audit,

your logging agent needs to be able to recover

from that situation meaning doing buffering

or maybe trying, if it fell from point A,

try to do some balancing, and try

point B or a different node.

So that balancing capability is coming up right now,

and also, we're happy to say that we

are implementing a new way to do filtering in a logging agent.

If you wanted to do some filtering of Fluentd,

you had to write your own Ruby script for filtering.

But if you wanted to do it on Fluentbit, like few weeks

ago, you had to write your C filter.

And for some people said, I cannot write C.

It's too complex, and I don't have the time, which is right.

We went in Europe at the beginning of this year in QCon,

and some people say, hey, GDPR is coming.

And I was not aware about GDPR.

OK, what is GDPR?

Explain it to me more about it.

And they said, OK, we need to obfuscate data.

We need to add some conditionals for the configuration

for Fluentbit and fix like A, B, C, D. OK, that is too complex.

We cannot maintain multiple plugins for different needs.

Yeah, because they said our logs are credit card transactions,

and they have the whole numbers, and we

need to obfuscate the data.

So we need a solution.

That is important.

So we said, OK, a new way to do filtering will be,

let's try to do some scripting.

You run Fluentbit as an agent, but also, when it starts,

you can start your own scripts, reading in Lua language, which

are quite performant.

And you can do all the data modifications

that you want without low performance penalty.

And also, we have an address here.

If you want to get more about all the news on Fluentbit 0.14

to be released, there's a link on the slides that you--

a form where you can sign up to get the news.

And we're taking the Lua script--

this is like a simple plugin.

Well, this is like a text file.

This is Lua, where basically, you

create a new record using Lua tables,

Centralized Logging Solution for Google Cloud Platform (Cloud Next '18... (3) centralizzato|registrazione|soluzione|per|Google|Cloud|piattaforma|Cloud|Next solución|de registro|centralizada|para|Google|Nube|Plataforma|Nube|Next Centralized Logging Solution for Google Cloud Platform (Cloud Next '18... (3) Google Cloud Platform向けログ一元管理ソリューション（Cloud Next '18... (3) 구글 클라우드 플랫폼을 위한 중앙 집중식 로깅 솔루션(클라우드 넥스트 '18... (3) Solução de registo centralizado para Google Cloud Platform (Cloud Next '18... (3) Централизованное решение для ведения журналов для Google Cloud Platform (Cloud Next '18... (3) Google Cloud Platform için Merkezi Günlükleme Çözümü (Cloud Next '18... (3) Google Cloud Platform 的集中日志记录解决方案 (Cloud Next '18...(3) Solución de Registro Centralizado para Google Cloud Platform (Cloud Next '18... (3) Soluzione di Logging Centralizzato per Google Cloud Platform (Cloud Next '18... (3)

and what we refer with context, because your application is |||относиться|||||| e|ciò che|noi|ci riferiamo|con|contesto|perché|tua|applicazione|è y|lo que|nosotros|nos referimos|con|contexto|porque|tu|aplicación|es y a lo que nos referimos con contexto, porque tu aplicación está e cosa intendiamo per contesto, perché la tua applicazione è

running in a pod. |||поду in esecuzione|in|un|pod corriendo|en|una|cápsula ejecutándose en un pod. in esecuzione in un pod.

That pod has a name. quel|pod|ha|un|nome esa|cápsula|tiene|un|nombre Ese pod tiene un nombre. Quella pod ha un nome.

That pod has an ID, an identification. ||||идентификатор|| quel|pod|ha|un|ID|un|identificazione esa|cápsula|tiene|un|identificación|una|identificación Ese pod tiene un ID, una identificación. Quella pod ha un ID, un'identificazione.

Also, you're running in a namespace. |||||пространство имен inoltre|stai|correndo|in|uno|namespace también|estás|corriendo|en|un|espacio de nombres Además, estás ejecutando en un espacio de nombres. Inoltre, stai eseguendo in uno spazio dei nomi.

If you deploy a pod, that pod belongs to a namespace. se|tu|distribuisci|un|pod|quel|pod|appartiene|a|un|namespace si|tú|despliegas|un|pod|ese|pod|pertenece|a|un|espacio de nombres Si despliegas un pod, ese pod pertenece a un espacio de nombres. Se distribuisci una pod, quella pod appartiene a uno spazio dei nomi.

It's running in a node, in a host. ||||узел||| esso è|in esecuzione|in|un|nodo|||host está|corriendo|en|un|nodo|en|un|anfitrión Está corriendo en un nodo, en un host. Sta girando in un nodo, in un host.

Maybe you added some labels and annotation to the pod, ||||||аннотация||| forse|tu|hai aggiunto|alcune|etichette|e|annotazioni|al||pod quizás|tú|agregaste|algunas|etiquetas|y|anotación|al|el|pod Quizás agregaste algunas etiquetas y anotaciones al pod, Forse hai aggiunto alcune etichette e annotazioni al pod,

this-- for example-- questo|per|esempio esto|por|ejemplo esto-- por ejemplo-- questo-- per esempio--

sorry. scusa lo siento lo siento. scusa.

Some labels saying, OK, [INAUDIBLE] ||||неразборчиво alcune|etichette|che dicono|ok|[illeggibile] algunas|etiquetas|diciendo|está bien|inaudible Algunas etiquetas dicen, OK, [INAUDIBLE] Alcune etichette dicono, OK, [INAUDIBLE]

for an application which is running in Kubernetes? |||||||Кубернетес per|un|applicazione|che|è|in esecuzione|in|Kubernetes para|una|aplicación|la cual|está|corriendo|en|Kubernetes ¿para una aplicación que se está ejecutando en Kubernetes? per un'applicazione che sta girando in Kubernetes?

This whole context also [INAUDIBLE] more complexity. ||||||сложность questo|intero|contesto|anche|[INAUDIBLE]|più|complessità este|todo|contexto|también|[INAUDIBLE]|más|complejidad Todo este contexto también [INAUDIBLE] más complejidad. Questo intero contesto aggiunge anche [INAUDIBLE] più complessità.

how things operate. come|cose|operano cómo|cosas|operan cómo funcionan las cosas. di come funzionano le cose.

server or the master server. server|o|il|master|server servidor|o|el|maestro|servidor servidor o del servidor maestro. server o dal server master.

And you need that your logging agent ||||||агент логирования e|tu|hai bisogno|che|tuo|registrazione|agente y|tú|necesitas|que|tu|de registro|agente Y necesitas que tu agente de registro E hai bisogno che il tuo agente di logging

And that's why the logging agent that you use and that e|questo è|perché|il|registrazione|agente|che|tu|usi|e|che y|eso es|por qué|el|de registro|agente|que|tú|usas|y|que Y por eso el agente de registro que usas y que Ed è per questo che l'agente di registrazione che usi e che

because of course, you cannot do this manually. |||||||вручную perché|di|certo|tu|non puoi|fare|questo|manualmente porque|de|curso|tú|no puedes|hacer|esto|manualmente porque, por supuesto, no puedes hacer esto manualmente. perché ovviamente non puoi farlo manualmente.

system, understand the messages, parse the messages-- ||||анализировать|| sistema|capire|i|messaggi|analizzare|i|messaggi sistema|entiende|los|mensajes|analiza|los|mensajes sistema, entender los mensajes, analizar los mensajes-- sistema, comprendere i messaggi, analizzare i messaggi--

which are in different formats-- ||||форматы che|sono|in|diversi|formati cuáles|están|en|diferentes|formatos que están en diferentes formatos-- che sono in formati diversi--

and correlate all the information together |сопоставить|||| e|correlare|tutte|le|informazioni|insieme y|correlaciona|toda|la|información|junta y correlacionar toda la información juntos e correlare tutte le informazioni insieme

with context coming from the API server. con|contesto|proveniente|da|il|API|server con|contexto|viniendo|de|el|API|servidor con el contexto proveniente del servidor API. con il contesto proveniente dal server API.

And that's Fluentd. e|questo è|Fluentd y|eso es|Fluentd Y eso es Fluentd. E questo è Fluentd.

has the whole extensions and integration |||расширения|| ha|le|intere|estensioni|e|integrazione tiene|la|totalidad|extensiones|y|integración tiene todas las extensiones e integraciones ha tutte le estensioni e integrazioni

your own database. tuo|proprio|database tu|propia|base de datos tu propia base de datos. al tuo database.

Maybe you're running on prem, or you have your own system forse|tu stai|eseguendo|su|locale|o|tu|hai|tuo|proprio|sistema quizás|estás|corriendo|en|prem|o|tú|tienes|tu|propio|sistema Tal vez estés ejecutando en local, o tengas tu propio sistema Forse stai eseguendo on-premise, o hai il tuo sistema

to store logs. per|memorizzare|log para|almacenar|registros para almacenar registros. per memorizzare i log.

Now log processing in Kubernetes is like the next step. Ahora el procesamiento de registros en Kubernetes es como el siguiente paso. Ora l'elaborazione dei log in Kubernetes è come il passo successivo.

If we think that we have just a single node, Si pensamos que solo tenemos un solo nodo, Se pensiamo di avere solo un singolo nodo,

well, we'll have the master and a single node. bueno, tendremos el maestro y un solo nodo. beh, avremo il master e un singolo nodo.

Fluentd, as a logging agent, needs to run as a DaemonSet. Fluentd, como agente de registro, necesita ejecutarse como un DaemonSet. Fluentd, come agente di logging, deve essere eseguito come un DaemonSet.

Do you know what a DaemonSet is? fare|tu|sai|cosa|un|DaemonSet|è (verbo auxiliar)|tú|sabes|qué|un|DaemonSet|es ¿Sabes qué es un DaemonSet? Sai cos'è un DaemonSet?

Are you familiar with pods? sei|tu|familiare|con|pod estás|tú|familiarizado|con|las cápsulas ¿Estás familiarizado con los pods? Sei familiare con i pod?

OK. OK está bien Está bien. OK.

A DaemonSet-- it's like a pod, but this pod un|DaemonSet|è|come|un|pod|ma|questo|pod un|DaemonSet|es|como|un|pod|pero|este|pod Un DaemonSet-- es como un pod, pero este pod Un DaemonSet-- è come un pod, ma questo pod

runs on every node of the cluster. gira|su|ogni|nodo|del|il|cluster corre|en|cada|nodo|del|el|clúster se ejecuta en cada nodo del clúster. gira su ogni nodo del cluster.

So if you append more nodes to your Kubernetes cluster, quindi|se|tu|aggiungi|più|nodi|al|tuo|Kubernetes|cluster entonces|si|tú|agregas|más|nodos|a|tu|Kubernetes|clúster Así que si agregas más nodos a tu clúster de Kubernetes, Quindi, se aggiungi più nodi al tuo cluster Kubernetes,

like a [INAUDIBLE] machine, and you already deploy it, come|una|[INAUDIBLE]|macchina|e|tu|già|distribuisci|esso como|una|inaudible|máquina|y|tú|ya|despliegas|eso como una máquina [INAUDIBLE], y ya lo has desplegado, come una macchina [INAUDIBLE], e lo hai già distribuito,

a DaemonSet, you're going to get a new pod with that DaemonSet un|DaemonSet|tu stai|andando|a|ottenere|un|nuovo|pod|con|quel|DaemonSet un|DaemonSet|vas a|a||recibir|un|nuevo|pod|con|ese|DaemonSet un DaemonSet, vas a obtener un nuevo pod con ese DaemonSet un DaemonSet, otterrai un nuovo pod con quel DaemonSet

So the way to work is that you deploy Fluentd as a DaemonSet. quindi|il|modo|a|lavorare|è|che|tu|distribuisci|Fluentd|come|un|DaemonSet entonces|la|manera|a|trabajar|es|que|tú|despliegas|Fluentd|como|un|DaemonSet Así que la forma de trabajar es que despliegas Fluentd como un DaemonSet. Quindi il modo di lavorare è che distribuisci Fluentd come un DaemonSet.

So the simple message that we started at the beginning quindi|il|semplice|messaggio|che|noi|abbiamo iniziato|all'|il|inizio entonces|el|simple|mensaje|que|nosotros|comenzamos|en|el|principio Así que el mensaje simple con el que comenzamos al principio Quindi il messaggio semplice con cui abbiamo iniziato all'inizio

Because it has Kubernetes, it has a host, pod name, pod ID, perché|esso|ha|Kubernetes|esso|ha|un|host|pod|nome|pod|ID porque|eso|tiene|Kubernetes|eso|tiene|un|host|pod|nombre|pod|ID Porque tiene Kubernetes, tiene un host, nombre de pod, ID de pod, Perché ha Kubernetes, ha un host, nome del pod, ID del pod,

because then in a Stackdriver or any database that you're using, perché|poi|in|un|Stackdriver|o|qualsiasi|database|che|stai|usando porque|entonces|en|una|Stackdriver|o|cualquier|base de datos|que|estás|usando porque entonces en un Stackdriver o cualquier base de datos que estés usando, perché poi in un Stackdriver o in qualsiasi database tu stia usando,

you don't want to query a show me the message that start tu|non|vuoi|a|interrogare|un|mostrare|mi|il|messaggio|che|inizia tú|no|quieres|a|consultar|un|mostrar|me|el|mensaje|que|empieza no quieres consultar un muéstrame el mensaje que comienza non vuoi interrogare un mostrarmi il messaggio che inizia

with "Hey Next." con|Hey|Next con|hey|next con "Hey Next." con "Hey Next."

and help the storage solution to create the data that you really e|aiuta|la|archiviazione|soluzione|a|creare|i|dati|che|tu|davvero y|ayuda|la|almacenamiento|solución|a|crear|los|datos|que|tú|realmente y ayudar a la solución de almacenamiento a crear los datos que realmente e aiutano la soluzione di archiviazione a creare i dati di cui hai veramente bisogno.

care about it and not query all of them. interessarsi|a|esso|e|non|interrogare|tutti|di|loro preocuparse|por|eso|y|no|consultar|todos|de|ellos preocúpate por ello y no consultes a todos. prendersene cura e non interrogarli tutti.

MARY KOES: Thanks. Mary|Koes|Grazie MARÍA|KOES|gracias MARY KOES: Gracias. MARY KOES: Grazie.

internal logging solution. interno|registrazione|soluzione interna|registro|solución solución de registro interno. soluzione di registrazione interna.

at Google-- presso|Google en|Google en Google-- di Google--

who use the logging tools that we build. quienes utilizan las herramientas de registro que construimos. che usano gli strumenti di registrazione che costruiamo.

So I wanted to share some lessons learned. Así que quería compartir algunas lecciones aprendidas. Quindi volevo condividere alcune lezioni apprese.

One is the value of structured logs, Una es el valor de los registros estructurados, Una è il valore dei log strutturati,

so not all logs are created equal. así que no todos los registros son iguales. quindi non tutti i log sono creati uguali.

a text payload of blah, blah, blah, purchased four widgets. un|testo|payload|di|blah|blah||acquistati|quattro|widget un|texto|carga|de|blah|blah||compró|cuatro|widgets una carga de texto de bla, bla, bla, compré cuatro widgets. un payload di testo di bla, bla, bla, acquistati quattro widget.

A structured log will have a lot of key value un|strutturato|registro|futuro|avrà|un|sacco|di|chiave|valore una|estructurada|bitácora|tendrá|mucho|muchas|clave|valor|| Un registro estructurado tendrá muchas claves y valores Un registro strutturato avrà molte coppie chiave-valore

pairs in JSON format. coppie|in|formato JSON|formato en formato JSON. in formato JSON.

it much easier to interact with your logs downstream as well. es mucho más fácil interactuar con tus registros más adelante. è molto più facile interagire con i tuoi log a valle.

Plus, you can do things in Stackdriver logging like say, Además, puedes hacer cosas en el registro de Stackdriver como decir, Inoltre, puoi fare cose nel logging di Stackdriver come dire,

show me the customer ID hash. muéstrame el hash del ID del cliente. mostrami l'hash dell'ID cliente.

I want that to be displayed easily, Quiero que eso se muestre fácilmente, Voglio che venga visualizzato facilmente,

If you do too little, then you don't have the data se|tu|fai|troppo|poco|allora|tu|non|hai|i|dati si|tú|haces|demasiado|poco|entonces|tú|no|tienes|los|datos Si haces muy poco, entonces no tienes los datos Se fai troppo poco, allora non hai i dati

And so trying to get that just right level of logs e|quindi|cercando|di|ottenere|quel|giusto|livello||di|log y|así|tratando|de|conseguir|eso|justo|correcto|nivel|de|registros Y así, tratar de obtener ese nivel justo de registros E quindi cercare di ottenere quel giusto livello di registrazioni

we found to be really helpful is to enforce noi|abbiamo trovato|a|essere|davvero|utile|è|a|far rispettare nosotros|encontramos|que|ser|realmente|útil|es|que|hacer cumplir encontramos que es realmente útil hacer cumplir abbiamo trovato molto utile imporre

through your code. attraverso|il tuo|codice a través de|tu|código a través de tu código. nel tuo codice.

and you expect somebody to actually investigate here, y esperas que alguien realmente investigue aquí, e ti aspetti che qualcuno indaghi effettivamente qui,

whereas maybe debug and info are less important. mientras que tal vez el depurado y la información son menos importantes. mentre forse il debug e le informazioni sono meno importanti.

And that makes it easier, when I filter, Y eso lo hace más fácil, cuando filtro, E questo rende più facile, quando filtro,

to quickly find the information that we care about. para encontrar rápidamente la información que nos importa. trovare rapidamente le informazioni che ci interessano.

we have metrics at a very fine-grained level, noi|abbiamo|metriche|a|un|molto|||livello nosotros|tenemos|métricas|a|un|muy|||nivel tenemos métricas a un nivel muy detallado, abbiamo metriche a un livello molto dettagliato,

statements? ¿declaraciones? dichiarazioni?

And you can slice and dice your data Y puedes segmentar y analizar tus datos E puoi suddividere i tuoi dati

in all sorts of ways, which can allow de todas las maneras posibles, lo que puede permitir in tutti i modi possibili, il che può permettere

you to iterate on your logging solution over time. que iteres en tu solución de registro con el tiempo. di iterare sulla tua soluzione di logging nel tempo.

which is the default agent in Stackdriver and also che|è|il|predefinito|agente|in|Stackdriver|e|anche cuál|es|el|predeterminado|agente|en|stackdriver|y|también que es el agente predeterminado en Stackdriver y también che è l'agente predefinito in Stackdriver e anche

we can think that Fluentd is more than just noi|possiamo|pensare|che|Fluentd|è|più|di|solo nosotros|podemos|pensar|que|Fluentd|es|más|de|solo podemos pensar que Fluentd es más que simplemente possiamo pensare che Fluentd sia più di

I would like to say that it is a whole ecosystem. io|condizionale di volere|piacere|a|dire|che|esso|è|un|intero|ecosistema yo|(verbo auxiliar)|gustaría|a|decir|que|eso|es|un|entero|ecosistema Me gustaría decir que es todo un ecosistema. Vorrei dire che è un intero ecosistema.

ingesting per second? ingerendo|al|secondo ingiriendo|por|segundo ingresando por segundo? ingestendo al secondo?

You need memory, CPU, and you are filtering data, tu|hai bisogno di|memoria|CPU|e|tu|sei|filtrando|dati tú|necesitas|memoria|CPU|y|tú|estás|filtrando|datos Necesitas memoria, CPU, y estás filtrando datos, Hai bisogno di memoria, CPU, e stai filtrando i dati,

and you have like 10 filters, that is time-consuming. e|tu|hai|circa|filtri|che|è|| y|tú|tienes|como|filtros|eso|es|| y tienes como 10 filtros, eso consume tiempo. e hai circa 10 filtri, il che richiede tempo.

driven by the community. guidato|dalla|la|comunità impulsado|por|la|comunidad impulsado por la comunidad. guidato dalla comunità.

space in a different way. spazio|in|un|diverso|modo espacio|de|una|diferente|manera espacio nativo de la nube de una manera diferente. in un modo diverso.

This is not like a replacement for Fluentd, questo|è|non|come|un|sostituto|per|Fluentd esto|es|no|como|un|reemplazo|para|Fluentd Esto no es un reemplazo para Fluentd, Questo non è un sostituto di Fluentd,

written in Perl and C language. scritto|in|Perl|e|C|linguaggio escrito|en|Perl|y|C|lenguaje escrito en Perl y lenguaje C. scritto in Perl e C.

is quite huge. è|abbastanza|grande es|bastante|enorme es bastante grande. è piuttosto vasto.

We have 700 plug-ins. noi|abbiamo|| nosotros|tenemos|| Tenemos 700 complementos. Abbiamo 700 plug-in.

and it's a sub-project of the CNCF. e|è|un|||di|la|CNCF y|es un|un|||de|la|cncf y es un subproyecto de la CNCF. ed è un sotto-progetto del CNCF.

is called 0.14. è|chiamata es|llamado se llama 0.14. si chiama 0.14.

The [INAUDIBLE] been around for more than three years, il|inaudibile|stato|in giro|per|più|di|tre|anni el|[INAUDIBLE]|ha estado|alrededor|por|más|de|tres|años El [INAUDIBLE] ha estado presente durante más de tres años, Il [INAUDIBLE] è presente da più di tre anni,

but we're trying to have the 1.0 at the end of the year. ma|stiamo|cercando|di|avere|la|alla|l'||||anno pero|estamos|tratando|de|tener|la|a|el|fin|de|el|año pero estamos tratando de tener la 1.0 a finales de año. ma stiamo cercando di avere la 1.0 entro la fine dell'anno.

It will not, at the beginning, this integration esso|futuro|non|a|il|inizio|questa|integrazione eso|va|a|al|el|principio|esta|integración No lo hará, al principio, esta integración Non lo farà, all'inizio, questa integrazione

is quite experimental. è|piuttosto|sperimentale es|bastante|experimental es bastante experimental. è piuttosto sperimentale.

It means that it doesn't have the whole features esso|significa|che|esso|non|ha|tutte|intere|funzionalità eso|significa|que|eso|no|tiene|las|todas|características Significa que no tiene todas las características Significa che non ha tutte le funzionalità

that Google Fluentd has, but we're working on that. che|Google|Fluentd|ha|ma|noi stiamo|lavorando|su|quello eso|Google|Fluentd|tiene|pero||trabajando|en|eso que tiene Google Fluentd, pero estamos trabajando en eso. che ha Google Fluentd, ma ci stiamo lavorando.

In logging, there is one specific feature in|registrazione|c'è|è|una|specifica|caratteristica en|registro|hay|una|una|específica|característica En el registro, hay una característica específica Nella registrazione, c'è una funzione specifica

that if you are dispatching your logs to your service, che|se|tu|sei|inviando|i tuoi|log|a|il tuo|servizio que|si|tú|estás|enviando|tus|registros|a|tu|servicio que si estás enviando tus registros a tu servicio, che se stai inviando i tuoi log al tuo servizio,

your logging agent needs to be able to recover tu agente de registro necesita ser capaz de recuperarse il tuo agente di registrazione deve essere in grado di recuperare

from that situation meaning doing buffering de esa situación, lo que significa hacer un almacenamiento en búfer da quella situazione, il che significa fare buffering

or maybe trying, if it fell from point A, o tal vez intentar, si cayó del punto A, o forse provare, se è caduto dal punto A,

try to do some balancing, and try intentar hacer algún balanceo, y tratar cercare di fare un po' di bilanciamento, e provare

point B or a different node. punto|B|o|un|diverso|nodo punto|B|o|un|diferente|nodo punto B o un nodo diferente. punto B o un nodo diverso.

ago, you had to write your C filter. fa|tu|dovevi|a|scrivere|tuo|C|filtro hace|tú|tenías|que|escribir|tu|C|filtro tenías que escribir tu filtro en C. fa, dovevi scrivere il tuo filtro in C.

It's too complex, and I don't have the time, which is right. è|troppo|complesso|e|io|non|ho|il|tempo|che|è|giusto es|demasiado|complejo|y|yo|no|tengo|el|tiempo|lo cual|es|correcto Es demasiado complejo, y no tengo el tiempo, lo cual es cierto. È troppo complesso e non ho tempo, il che è vero.

OK, what is GDPR? OK|cosa|è|GDPR está bien|qué|es|GDPR OK, ¿qué es el GDPR? OK, cos'è il GDPR?

Explain it to me more about it. spiega|lo|a|me|più|riguardo a|esso explícamelo|eso|a|mí|más|sobre|ello Explícame más sobre eso. Spiegami di più a riguardo.

for Fluentbit and fix like A, B, C, D. OK, that is too complex. per|Fluentbit|e|sistemare|come|A|B|C|D|OK|quello|è|troppo|complesso para|Fluentbit|y|arreglar|como|A|B|C|D|está bien|eso|es|demasiado|complejo para Fluentbit y arreglar como A, B, C, D. Está bien, eso es demasiado complejo. per Fluentbit e sistemare come A, B, C, D. OK, è troppo complesso.

need to obfuscate the data. dobbiamo|a|offuscare|i|dati necesito|que|ofuscar|los|datos necesitamos ofuscar los datos. dobbiamo offuscare i dati.

That is important. quello|è|importante eso|es|importante Eso es importante. Questo è importante.

are quite performant. sono|abbastanza|performanti son|bastante|eficientes son bastante eficientes. sono abbastanza performanti.

to be released, there's a link on the slides that you-- a|essere|rilasciato|c'è|un|link|su|le|diapositive|che|tu para|ser|liberado|hay|un|enlace|en|las|diapositivas|que|tú que se lanzará, hay un enlace en las diapositivas que tú-- che sarà rilasciato, c'è un link nelle diapositive che tu--

SENT_CWT:ANplGLYU=5.41 PAR_TRANS:gpt-4o-mini=5.37 PAR_TRANS:gpt-4o-mini=3.11 PAR_CWT:AvJ9dfk5=7.99 es:ANplGLYU it:AvJ9dfk5 openai.2025-02-07 ai_request(all=130 err=3.85%) translation(all=260 err=0.00%) cwt(all=2014 err=10.48%)