Skip to content

Commit 2ea8020

Browse files
authored
Merge pull request #428 from adithyaakrishna/bug/fix-broken-links
[Bug] - Fixed Broken Links
2 parents 115fffd + ceb44f8 commit 2ea8020

File tree

3 files changed

+23
-22
lines changed

3 files changed

+23
-22
lines changed

installation/install-by-deb.md

Lines changed: 13 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -88,17 +88,19 @@ Use `/lib/systemd/system/td-agent` script to `start`, `stop`, or `restart` the a
8888
$ sudo systemctl start td-agent.service
8989
$ sudo systemctl status td-agent.service
9090
● td-agent.service - td-agent: Fluentd based data collector for Treasure Data
91-
Loaded: loaded (/lib/systemd/system/td-agent.service; disabled; vendor preset: enabled)
92-
Active: active (running) since Thu 2017-12-07 15:12:27 PST; 6min ago
93-
Docs: https://docs.treasuredata.com/articles/td-agent
94-
Process: 53192 ExecStart = /opt/td-agent/embedded/bin/fluentd --log /var/log/td-agent/td-agent.log --daemon /var/run/td-agent/td-agent.pid (code = exited, statu
95-
Main PID: 53198 (fluentd)
96-
CGroup: /system.slice/td-agent.service
97-
├─53198 /opt/td-agent/embedded/bin/ruby /opt/td-agent/embedded/bin/fluentd --log /var/log/td-agent/td-agent.log --daemon /var/run/td-agent/td-agent
98-
└─53203 /opt/td-agent/embedded/bin/ruby -Eascii-8bit:ascii-8bit /opt/td-agent/embedded/bin/fluentd --log /var/log/td-agent/td-agent.log --daemon /v
99-
100-
Dec 07 15:12:27 ubuntu systemd[1]: Starting td-agent: Fluentd based data collector for Treasure Data...
101-
Dec 07 15:12:27 ubuntu systemd[1]: Started td-agent: Fluentd based data collector for Treasure Data.
91+
Loaded: loaded (/lib/systemd/system/td-agent.service; enabled; vendor preset: enabled)
92+
Active: active (running) since Tue 2022-09-20 05:28:25 JST; 1 week 0 days ago
93+
Docs: https://docs.treasuredata.com/display/public/PD/About+Treasure+Data%27s+Server-Side+Agent
94+
Main PID: 2417 (fluentd)
95+
Tasks: 8 (limit: 38328)
96+
Memory: 52.2M
97+
CPU: 56.868s
98+
CGroup: /system.slice/td-agent.service
99+
├─2417 /opt/td-agent/bin/ruby /opt/td-agent/bin/fluentd --log /var/log/td-agent/td-agent.log --daemon /var/run/td-agent/td-agent.pid
100+
└─2420 /opt/td-agent/bin/ruby -Eascii-8bit:ascii-8bit /opt/td-agent/bin/fluentd --log /var/log/td-agent/td-agent.log --daemon /var/run/td-agent/t>
101+
102+
Sept 9 20 05:28:24 Ryzen systemd[1]: Starting td-agent: Fluentd based data collector for Treasure Data...
103+
Sept 9 20 05:28:25 Ryzen systemd[1]: Started td-agent: Fluentd based data collector for Treasure Data.
102104
```
103105

104106
To customize `systemd` behavior, put your `td-agent.service` in `/etc/systemd/system`.

installation/install-by-rpm.md

Lines changed: 9 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -68,17 +68,16 @@ Use `/usr/lib/systemd/system/td-agent` script to `start`, `stop`, or `restart` t
6868
$ sudo systemctl start td-agent.service
6969
$ sudo systemctl status td-agent.service
7070
● td-agent.service - td-agent: Fluentd based data collector for Treasure Data
71-
Loaded: loaded (/lib/systemd/system/td-agent.service; disabled; vendor preset: enabled)
72-
Active: active (running) since Thu 2017-12-07 15:12:27 PST; 6min ago
73-
Docs: https://docs.treasuredata.com/articles/td-agent
74-
Process: 53192 ExecStart = /opt/td-agent/embedded/bin/fluentd --log /var/log/td-agent/td-agent.log --daemon /var/run/td-agent/td-agent.pid (code = exited, statu
75-
Main PID: 53198 (fluentd)
71+
Loaded: loaded (/usr/lib/systemd/system/td-agent.service; enabled; vendor preset: disabled)
72+
Active: active (running) since Tue 2022-09-27 06:14:36 UTC; 1s ago
73+
Docs: https://docs.treasuredata.com/display/public/PD/About+Treasure+Data%27s+Server-Side+Agent
74+
Process: 33953 ExecStart=/opt/td-agent/bin/fluentd --log $TD_AGENT_LOG_FILE --daemon /var/run/td-agent/td-agent.pid $TD_AGENT_OPTIONS (code=exited, status=0>
75+
Main PID: 33959 (fluentd)
76+
Tasks: 10 (limit: 4958)
77+
Memory: 78.1M
7678
CGroup: /system.slice/td-agent.service
77-
├─53198 /opt/td-agent/embedded/bin/ruby /opt/td-agent/embedded/bin/fluentd --log /var/log/td-agent/td-agent.log --daemon /var/run/td-agent/td-agent
78-
└─53203 /opt/td-agent/embedded/bin/ruby -Eascii-8bit:ascii-8bit /opt/td-agent/embedded/bin/fluentd --log /var/log/td-agent/td-agent.log --daemon /v
79-
80-
Dec 07 15:12:27 ubuntu systemd[1]: Starting td-agent: Fluentd based data collector for Treasure Data...
81-
Dec 07 15:12:27 ubuntu systemd[1]: Started td-agent: Fluentd based data collector for Treasure Data.
79+
├─33959 /opt/td-agent/bin/ruby /opt/td-agent/bin/fluentd --log /var/log/td-agent/td-agent.log --daemon /var/run/td-agent/td-agent.pid
80+
└─33962 /opt/td-agent/bin/ruby -Eascii-8bit:ascii-8bit /opt/td-agent/bin/fluentd --log /var/log/td-agent/td-agent.log --daemon /var/run/td-agent/td>
8281
```
8382

8483
To customize `systemd` behavior, put your `td-agent.service` in `/etc/systemd/system`.

troubleshooting-guide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ One of Fluentd's big strengths is it's ability to parse logs into a standardized
7171

7272
**Suggestions:**
7373

74-
* Use online tools such as [Rubular.com](https://rubular.com) and [fluentular](https://fluentular.com) with a sample of the log file as well as the regex. This will give you a clear example of what the end match groups will look like as well as allow you to validate Ruby timeformat.
74+
* Use online tools such as [Rubular.com](https://rubular.com) and [fluentular](https://fluentular.herokuapp.com/) with a sample of the log file as well as the regex. This will give you a clear example of what the end match groups will look like as well as allow you to validate Ruby timeformat.
7575
* Check existing parsers for well-known formats you may be able to use one of the parsers that Fluentd already includes [https://docs.fluentd.org/parser](https://docs.fluentd.org/parser). Note: you can also checkout [Fluent Bit parsers](https://github.com/fluent/fluent-bit/blob/master/conf/parsers.conf) for additional examples as both projects use Ruby regular expressions
7676
* Check multi-line logs have proper configuration settings. Multi-line logs need to have specific settings set in the parser to work properly, make sure these are all set.
7777

0 commit comments

Comments
 (0)