Log remote submitter's IP addresses

Open
#878 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
go
Domain
api, observability

Research direction

No files or tests are identified in the issue. Start by locating the request handling and logging for addChain or similar remote actions, then determine how the submitter IP is available there. Done means the remote submitter's IP is included in logs for those actions and the relevant logging behavior is verified.

Written by the indexing model from the issue text.

Description

enhancement

Description

Currently TesseraCT doesn't track remote submitter's IP in the logs. So we should add remote submitter's IP in the logs (to track addChain or similar actions).

Dominant language
Go
Stars
37
Forks
18
Avg merge
19h 22m
Merged PRs (30d)
15

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from transparency-dev/tesseract

All issues in transparency-dev/tesseract

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.