[AMBARI-22842] Provide field / component UI metadata from backend

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.7.0
• Fix Version/s: 2.7.0
• Component/s: ambari-logsearch
• Labels: pull-request-available
• Epic Link: Log Search GA
• Assignee: Oliver Szabo
• Reporter: Oliver Szabo
• Created: 24/Jan/18 16:17
• Updated: 12/Sep/18 09:22
• Resolved: 19/Feb/18 11:25

Description

Adding new options for the backend to get field / component metadata:

logsearch.web.service_logs.group.labels=k1:v1,k2:v2
logsearch.web.service_logs.component.labels=k1:v1,k2:v2
logsearch.web.service_logs.field.labels=k1:v1,k2:v2
logsearch.web.service_logs.field.excludes=v1,v2,v3
logsearch.web.service_logs.field.visible=v1,v2,v3
logsearch.web.service_logs.field.filterable.excludes=v1,v2
logsearch.web.audit_logs.component.labels=k1:v1,k2:v2
logsearch.web.audit_logs.field.labels=K1#k1:v1,k2:v2;K2#k1:v1,k3:v3
logsearch.web.audit_logs.field.common.labels=k1:v1,k2:v2
logsearch.web.audit_logs.field.visible=k1:v1,v2,v3;k2:v1,v2
logsearch.web.audit_logs.field.common.visible=v1,v2,v3
logsearch.web.audit_logs.field.excludes=k1:v1,v2,v3;k2:v1,v2
logsearch.web.audit_logs.field.common.excludes=v1,v2,v3
logsearch.web.audit_logs.field.filterable.excludes==k1:v1,v2,v3;k2:v1,v2
logsearch.web.audit_logs.field.common.filterable.common.excludes=v1,v2,v3
logsearch.web.labels.fallback.enabled=true
logsearch.web.labels.service_logs.field.fallback.prefixes=ws_,std_,sdi_

Field metadata:

• name: real field name
• label (visible name on the UI for the field)
• visible (by default it should be visible in tables)
• filterable (it can be filterable from the searchbox) - always true by default, if not set, contains everything which is not excluded
  (audit field metadata has common values, because different metadata can be used for different audit types)
  with exclude properties you can remove fields from the response, those are also not filtered, but you can set fields to non-filtered if they are in the response with filterable.exclude options

Component metadata:

• name - label map: real component name with the name that should be seen on the UI
  for service component there is an additional field: group, different components can be grouped together (like: metrics_collector and metrics_grafana can be in the same AMS group)

`api/v1/service/logs/schema/fields` and `api/v1/audit/logs/schema/fields` will contain field metadata
`api/v1/service/logs/components` and `api/v1/audit/logs/components` will contain component metadata

Issue Links

• links to: GitHub Pull Request #183