influxdata / influxdata/influxdb
syslog does not get syslogging but time series logging
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
I wonder if someone even looks at your own logging. This is just crap being received on syslog server. How difficult is it to consult your own logs on your own server, before implementing such a feature.
Sep 24 11:11:19 db1 influxd-systemd-start.sh: ts=2022-09-24T09:11:19.394943Z lvl=warn msg="Error compacting TSM files" log_id=0d7LeN30000 engine=tsm1 tsm1_strategy=full tsm1_optimize=false trace_id=0d7gT8mW000 op_name=tsm1_compact_group db_shard_id=15 error="write /var/lib/influxdb/data/collections/autogen/15/000000546-000000003.tsm.tmp: no space left on device"
flaw.
influxdb-1.8.10-1.x86_64
Contributor guide
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.
Research direction
Reproduce the report with InfluxDB 1.8.10 and inspect the sample emitted by influxd-systemd-start.sh at the syslog server. First determine whether the issue is the message format or the underlying no-space error; done requires a clearly improved or corrected syslog result, verified against the reported output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- databases, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100