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
3 months agoMicaela
2 months agoCarmen
2 months agoRaylene
2 months agoLisbeth
2 months agoPaola
3 months agoTheodora
3 months agoCordie
2 months agoEulah
2 months agoJarvis
3 months agoJeannine
3 months agoLynette
3 months agoNada
2 months agoPauline
3 months agoVallie
3 months agoAllene
4 months agoElliot
3 months agoMatt
3 months agoVal
3 months agoMaddie
3 months agoBlossom
4 months agoAvery
4 months agoArgelia
4 months ago