cloudfoundry / cloudfoundry/cloud_controller_ng
Syslog drains no longer update application name changes without a restart
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 207
- Forks
- 373
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 56
Description
I am a Platform Architect submitting this for a customer.
Issue
Syslog org.space.appname tag is not updated when an application name is changed via a syslog drain.
Context
Previous to PAS 2.8, an application could be renamed and the "org.space.appname" tag in syslog messages sent through a syslog drain would be dynamically updated. As of PAS 2.8, presumably because of a change in syslog adapter, these tags are no longer updated when an application name is changed unless the application is restarted/restaged.
Steps to Reproduce
Deploy an application
Bind to a syslog drain
Observe the syslog events
Rename the application
Observe the syslog events
Expected result
The org.space.appname tag would change on new syslog events after the application name is changed.
Current result
The "appname" tag remains the old application name after the application name is changed.
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
Start with the syslog adapter and trace how application name changes reach new syslog drain events. Reproduce the deploy, bind, rename, and event-observation sequence described in the issue, then verify that subsequent events use the new org.space.appname value without restarting or restaging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend, observability-sre
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100