This is exciting! Would be useful if an integration could provide a lambda function that receives (batches of) logs, instead of sending directly to an external receiver. This would be more flexible to process/format the data.
Forward all your logs to your favorite logging platform today.
◆ Set up @LogDNA and @datadoghq in seconds.
◆ Or build your own log pipelines with our open API.
◆ Edge, static, function and build logs.https://zeit.co/blog/log-drains
-
-
-
Indeed. One problem we ran into with that was cost, but what you are suggesting absolutely makes sense.
- Još 5 drugih odgovora
Novi razgovor -
-
-
I was just about to need this! I feel like you guys are running out in front of me, laying down a red carpet for me to walk on. Awesome work!!
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Sadly this doesn't appear to be any different from the previous version. Missing vital information from request headers like "referer". Needs to be added to be useful. Unfortunately useless for us without them. I have been waiting since December for this and it ended up the same.
- Kraj razgovora
Novi razgovor -
-
-
Thanks for giving us this desired feature. I would like to know when splunk log drains integration will be available?
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Awesome! Is there a way to have the runtime logs in JSON format like the edge nextwork traffic logs? Or do you have some example of pipeline/processor to extract the meta data and the lambda output?pic.twitter.com/c9dSzKjPS4
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.