Possibly incorrect output from syslog export?
harukizaemon opened this issue · comments
Simon Harris commented
All my .service
files contain the following:
Environment=PORT=%i
SyslogIdentifier=%n
Is that a bug? Have I don't something wrong? Or is that expected?
Thanks
David Dollar commented
Most of the service exporters were contributed so I'm honestly not sure. Is something broken?
Brandon Hilkert commented
@harukizaemon That seems expected. They're filled in at runtime. Here's sample of my syslog
:
Feb 4 02:23:31 ip-10-0-1-158 bark-web@5000.service[20665]: * Pruning Bundler environment
Feb 4 02:23:31 ip-10-0-1-158 bark-web@5000.service[20665]: [20665] Puma starting in cluster mode...
Feb 4 02:23:31 ip-10-0-1-158 bark-web@5000.service[20665]: [20665] * Version 3.6.2 (ruby 2.3.3-p222), codename: Sleepy Sunday Serenity
Feb 4 02:23:31 ip-10-0-1-158 bark-web@5000.service[20665]: [20665] * Min threads: 5, max threads: 5
Feb 4 02:23:31 ip-10-0-1-158 bark-web@5000.service[20665]: [20665] * Environment: production
Feb 4 02:23:31 ip-10-0-1-158 bark-web@5000.service[20665]: [20665] * Process workers: 10
Feb 4 02:23:31 ip-10-0-1-158 bark-web@5000.service[20665]: [20665] * Phased restart available
Feb 4 02:23:31 ip-10-0-1-158 bark-web@5000.service[20665]: [20665] * Listening on tcp://0.0.0.0:5000
Feb 4 02:23:31 ip-10-0-1-158 bark-web@5000.service[20665]: [20665] * Listening on unix:///home/ubuntu/bark/tmp/sockets/puma.sock
Feb 4 02:23:31 ip-10-0-1-158 bark-web@5000.service[20665]: [20665] Use Ctrl-C to stop
Simon Harris commented
Yeah. seems to be working just fine. Sorry!