[jira] [Created] (SENSSOFT-284) "userid" field seems to impact ability to correctly map 'details' field for tab meta data.

["Joshua Poore (JIRA)" <ji...@apache.org>]

Joshua Poore created SENSSOFT-284:
-------------------------------------

             Summary: "userid" field seems to impact ability to correctly map 'details' field for tab meta data.
                 Key: SENSSOFT-284
                 URL: https://issues.apache.org/jira/browse/SENSSOFT-284
             Project: SensSoft
          Issue Type: Bug
          Components: UserALE.js
    Affects Versions: UserALE.js 1.0.0
         Environment: CentOS, JavaScript, Logstash, Elastic
            Reporter: Joshua Poore
            Assignee: Rob Foley
             Fix For: UserALE.js 0.2.0


The problem is: the ‘details’ field in tab transitions doesn’t map uniformly when different userids are passed to the logs via the plugin interface (firefox). Specifically, details appears as a searchable field with no meta data, where we would expect the various subtitles to map as details.[].

It affects very simple visualizations in Kibana for tracking page visits (details.title.keyword) by userid. pageUrl does map (though this is not part of 'details'). details.title however is more pragmatic for tabulating visits to domains without munging through pageUrls.

Here are the details:

1. When userid is left at default (‘nobody’), details.title.keyword maps correctly. details.title appears as a searchable field and details.title.keyword aggregates correctly in visualizations in kibana.

2. When userid is changed to any other strings, ‘details’ appears in logs as an empty field with a warning “(paraphrase) data is available for search but will not populate, consider refreshing Index mappings” in kibana’s discover tab.

3. If userid is changed back to "nobody" from some other value, 'details' appears to map along its subfields correctly (esp details.title)

Testing details:
 # Tested on 3 different clients:
 ## Confirmed that when userid was set to nobody, logs from each different client (hostname) correctly mapped details.title.
 ## Confirmed that when userid was set to another value, logs with userid==[string] did not have valid data that could be read in "explore" tab of kibana, and did not aggregate through table visualization.

NOTE: Untested in script tag method



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)