[
https://issues.apache.org/jira/browse/AMBARI-22842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivér Szabó updated AMBARI-22842:
----------------------------------
Description:
Adding new options for the backend to get field / component metadata:
{code:java}
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_
{code}
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
was:
Adding new options for the backend to get field / component metadata:
{code:java}
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_
logsearch.web.labels.service_logs.field.fallback.prefixes=sdi_
{code}
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
> Provide field / component UI metadata from backend
> --------------------------------------------------
>
> Key: AMBARI-22842
> URL: https://issues.apache.org/jira/browse/AMBARI-22842
> Project: Ambari
> Issue Type: Bug
> Components: ambari-logsearch
> Affects Versions: 2.7.0
> Reporter: Olivér Szabó
> Assignee: Olivér Szabó
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0
>
> Original Estimate: 48h
> Time Spent: 4.5h
> Remaining Estimate: 43.5h
>
> Adding new options for the backend to get field / component metadata:
> {code:java}
> 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_
> {code}
> 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
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
