[ 
https://issues.apache.org/jira/browse/SENSSOFT-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joshua Poore resolved SENSSOFT-342.
-----------------------------------
    Resolution: Not A Problem

Queried Elasticsearch directly 
{code:java}
http://localhost:9200/userale/_search?q=logType:interval
{code}
Interval Logs are indeed being written to the UserALE index:
{code:java}
_index  "userale"
_type   "doc"
_id     "olhTsmkBlFKxlUEzn0FV"
_score  1.0208666
_source 
userId  "nobody"
type    "mouseover"
targetChange    true
userAction      false
useraleVersion  "1.1.0"
target  "a"
pageTitle       "Branches · apache/incubator-senssoft"
@timestamp      "2019-03-25T00:50:18.179Z"
pageReferrer    "https://github.com/apache/incubator-senssoft/projects";
typeChange      false
startTime       1553475010012
endTime 1553475013868
sessionID       "session_1553474988111"
host    "172.18.0.1"
minor_ver       "1"
count   14
pageUrl "https://github.com/apache/incubator-senssoft/branches";
toolName        "test_app"
logType "interval"
duration        3856
toolVersion     null
patch_ver       "0"
path    […]
major_ver       "1"{code}
However, interval logs do not have a "clientTime" field–its contrary to their 
nature, they use startTime and endTime. Therefore, when users select 
"clientTime" for indexing, these logs do not appear in the *userale index in 
Kibana. Pushed instructions for users to select "@timestamp" if they want to 
view interval logs. This solution makes sense conceptually and pragmatically. 

 

> No interval Logs Appearing in Elastic
> -------------------------------------
>
>                 Key: SENSSOFT-342
>                 URL: https://issues.apache.org/jira/browse/SENSSOFT-342
>             Project: SensSoft
>          Issue Type: Bug
>          Components: builds
>    Affects Versions: SensSoft 1.0
>         Environment: Elastic 6.5
>            Reporter: Joshua Poore
>            Assignee: Joshua Poore
>            Priority: Major
>             Fix For: SensSoft 1.0
>
>
> Interval logs are being written but do not appear in Elastic.
> Confirmed that they are being written using example server, via script tags 
> and web extensions.
> NOTE: Need to replicate on 6.2.2. elastic build.
> Hypothesis: missed some update to index in migration to Elastic 6.5–can see 
> that "interval" is a searchable property in Kibana filters.



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

Reply via email to