influxdata / influxdata/docs-v2
Replication logs
@sanderson is already working on this.
Since Jun 17, 2022.
- Dominant language
- JavaScript
- Stars
- 82
- Forks
- 326
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 82
Description
As part of the "Logging" item in this issue: https://github.com/influxdata/docs-v2/issues/827
I wanted to throw out a "strawman" for documenting logs to look out for. My thoughts on this are to simply list useful troubleshooting logs (essentially "bad" logs) and break down the list of possible ones by core functionality and possibly by the log level you should expect to see each. Here is an example of doing it for replications:
**Error:**
- Queue is full
- Segment read error
- Failed to initialize replication stream durable queue
- Failed to remove durable queue during partial delete cleanup
- Error in replication stream
- Error creating replications queue scanner
- Error in replication queue scanner
**Info:**
- Segment read error
- Problem reading from queue
**Debug:**
- Remote write error
Idk if this the correct organization once zoom out to the rest of the logs but seemed like a fair starting example.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.