A developer is writing logs through the Log Service API, and can see via the Logstore monitorin metrics that write traffic is about 10 MB/s, but a 403 error is reported during the writing process. Which of these is a possible cause?
Ah, the age-old battle of man versus machine. Or in this case, dPaolaloper versus Logstore. My money's on B) - those partitions can only handle so much before they start throwing 403s around.
I don't know, guys. This question is making my head spin. Maybe the dPaolaloper should try writing their logs with a T-Rex instead of an API? Just a thought.
B) seems like the most likely cause. If the write throughput of a single partition is limited, the 10 MB/s traffic could exceed that limit, resulting in the 403 error.
Rosina
5 months agoMicaela
4 months agoCarmen
4 months agoRaylene
4 months agoLisbeth
4 months agoPaola
5 months agoTheodora
5 months agoCordie
4 months agoEulah
5 months agoJarvis
5 months agoJeannine
6 months agoLynette
6 months agoNada
5 months agoPauline
5 months agoVallie
5 months agoAllene
6 months agoElliot
5 months agoMatt
5 months agoVal
5 months agoMaddie
6 months agoBlossom
6 months agoAvery
6 months agoArgelia
6 months ago