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
22 days agoPaola
25 days agoTheodora
27 days agoEulah
4 days agoJarvis
13 days agoJeannine
1 months agoLynette
1 months agoNada
5 days agoPauline
9 days agoVallie
16 days agoAllene
1 months agoElliot
10 days agoMatt
25 days agoVal
28 days agoMaddie
1 months agoBlossom
1 months agoAvery
2 months agoArgelia
2 months ago