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