Make cloud.gov API logs more reader-friendly - Githubissues

fecgov / fecfile-web-api

Back-end API for FECfile application

Other

8 stars 2 forks source link

Make cloud.gov API logs more reader-friendly #1195

Open exalate-issue-sync[bot] opened 2 weeks ago

exalate-issue-sync[bot] commented 2 weeks ago

Eliminate extras for info logs, make sure we have enough info for exceptions

identify useful structlog fields to keep (e.g., user_id, request_id)
remove unuseful fields (e.g., child_task_name, _record)
ensure that exceptions still have enough information for developers to act off of


  level='info' event='task_enqueued' logger='django_structlog.celery.receivers' child_task_id='7ba50be2-e2d2-4ce6-bf13-ab02d38d6cbe' child_task_name='fecfiler.web_services.summary.tasks.calculate_summary' routing_key='celery' user_id='83f441d0-f5a8-41b4-ada2-f31879f3143c' ip='2601:152:c02:c610:b1a6:56de:7f01:1684' request_id='00ee403b-693b-42b1-8024-40b26bd65437' _record= _from_structlog=True

QA Notes

Screenshot of new logs will be provided

DEV Notes

null

Design

null

See full ticket and images here: FECFILE-1777

exalate-issue-sync[bot] commented 1 week ago

akhorsand commented: [~accountid:712020:2a1493e5-adee-45bd-b27e-868a5c8d3f62] this is assigned for Sprint 52 - can you add some detail and get it ready for pointing? Thanks!