Details
-
Feature
-
Resolution: Unresolved
-
Normal
-
None
-
False
-
None
-
False
-
Not Selected
-
0
-
0%
-
Release Note Not Required
-
0
Description
- Proposed title of this feature request
- Enable custom labeling for evet router data
- What is the nature and description of the request?
- The cluster events need to be sent outside of the cluster to a central logging end event store. Additional labels for the events are needed for better identification of the source of the event.
- Why does the customer need this? (List the business requirements here)
- The events are sent to an external store. It needs to be indexed and searchable. Events are related to application logs. The developers and application administrators need to be able to associate the app logs with the events. The application only says that the application fails but it does not say why the application has not started at all. The app logs ingest labels from the namespace labels and then the labels can be used for indexing. The same functionality is needed for events. For example, a namespace can be labeled as env=dev, app=bankingui. If the events ingest these logs, the admins can search for app=bankingui and specific env like dev, test, prod...
- List any affected packages or components.
- Event router
Attachments
Issue Links
- depends on
-
LOG-3987 Add metadata to kubernetes event logs
-
- Planning
-
