Hi I'm looking for some of the ways where i can contribute to team's success outside of my sprint work and also improve my skills
I'm a backend java developer. I know this is vague.
One of the issue is that our splunk log retention is only 10 days and debugging prod issues is a pain when there are no splunk logs - any suggestions on how to address it( Our splunk admin team doesnt give an exception)
another issue :
We do not have write access to prod dynamo db tables and currently i built an api to write to it through application- But it can be error prone as we enter info through swagger pages
apart from above 2 , can you please share some suggestions (I know its very team specific) but any pointers would be appreciated
I'm guessing that you can't maintain a longer Splunk retention because it would be cost-prohibitive. Could that be an opportunity?
You could categorize the error codes or messages into a frequency counter. Then you could plot how often you see various errors or codes. Spikes in a specific error/log message could be valuable for on-call teams:
Then you could create alerts and documentation around this. if you can get adoption from other engineers, this sounds like lots of impact!