April 2014 - overlord-issues - Jboss List Archives

[JBoss JIRA] (SRAMP-382) Support EAP 6.3

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/SRAMP-382?page=com.atlassian.jira.plugin.... ] Gary Brown commented on SRAMP-382: ---------------------------------- Hi Brett - yes, renaming the module is fine. [~ewittmann] and I had already discussed this, as the tomcat and jetty modules are named after just the major versions, so we agreed that eap and fuse modules should do the same. This jira was just a placeholder for any work that may need to be done to remain compatible with 6.3. However with any luck there should be no issues. btw - when changing the artifact id, you will need to update both the sramp installer and overlord installer (https://github.com/Governance/overlord). > Support EAP 6.3 > --------------- > > Key: SRAMP-382 > URL: https://issues.jboss.org/browse/SRAMP-382 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Brett Meyer > Fix For: 0.5.0 - API Management > > > Add support for EAP 6.3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-382) Support EAP 6.3

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-382?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on SRAMP-382: ----------------------------------- CC [~eric.wittmann] > Support EAP 6.3 > --------------- > > Key: SRAMP-382 > URL: https://issues.jboss.org/browse/SRAMP-382 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Brett Meyer > Fix For: 0.5.0 - API Management > > > Add support for EAP 6.3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-382) Support EAP 6.3

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-382?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on SRAMP-382: ----------------------------------- [~objectiser], could we simply rename (or deprecate) s-ramp-server-eap61 and create s-ramp-server-eap6? Looking through it, that should work for 6.1.0 through 6.3.0 (and possibly 6.4.0, if there is one). Unless I'm missing something, I don't see anything in s-ramp-server-eap61 that would need to be changed for 6.3. Thoughts? > Support EAP 6.3 > --------------- > > Key: SRAMP-382 > URL: https://issues.jboss.org/browse/SRAMP-382 > Project: S-RAMP > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Gary Brown > Assignee: Brett Meyer > Fix For: 0.5.0 - API Management > > > Add support for EAP 6.3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-428) Time filter on Kibana causes no data to be displayed

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-428?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-428: ---------------------------------- Yes, changing the timepicker setting to 'timestamp' solved the problem. So this is fine for now. > Time filter on Kibana causes no data to be displayed > ---------------------------------------------------- > > Key: RTGOV-428 > URL: https://issues.jboss.org/browse/RTGOV-428 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > Attachments: dashsettings.png, Screen Shot 2014-04-14 at 12.59.00.png > > > When setting the time filter, it causes no data to be displayed, even though there is data available for that time frame. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-428) Time filter on Kibana causes no data to be displayed

by ivan mckinley (JIRA)

[ https://issues.jboss.org/browse/RTGOV-428?page=com.atlassian.jira.plugin.... ] ivan mckinley commented on RTGOV-428: ------------------------------------- Wasn't sure whether @timestamp was supposed to map onto the timestamp value for the document being viewed? > neither am i now. I try review this later . Can you jsut confirm changing the timepicker setting to "timestamp" resolved your issue > Time filter on Kibana causes no data to be displayed > ---------------------------------------------------- > > Key: RTGOV-428 > URL: https://issues.jboss.org/browse/RTGOV-428 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > Attachments: dashsettings.png, Screen Shot 2014-04-14 at 12.59.00.png > > > When setting the time filter, it causes no data to be displayed, even though there is data available for that time frame. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-428) Time filter on Kibana causes no data to be displayed

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-428?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-428: ----------------------------- Attachment: dashsettings.png The problem wasn't on the histogram's settings, which used the 'timestamp' time field (as you have shown), but the dashboard settings - which previously used @timestamp. Wasn't sure whether @timestamp was supposed to map onto the timestamp value for the document being viewed? > Time filter on Kibana causes no data to be displayed > ---------------------------------------------------- > > Key: RTGOV-428 > URL: https://issues.jboss.org/browse/RTGOV-428 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > Attachments: dashsettings.png, Screen Shot 2014-04-14 at 12.59.00.png > > > When setting the time filter, it causes no data to be displayed, even though there is data available for that time frame. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-428) Time filter on Kibana causes no data to be displayed

by ivan mckinley (JIRA)

[ https://issues.jboss.org/browse/RTGOV-428?page=com.atlassian.jira.plugin.... ] ivan mckinley updated RTGOV-428: -------------------------------- Attachment: Screen Shot 2014-04-14 at 12.59.00.png Screenshot kibana histogram config for responsetime object. Rtgov-mappping.json. Outlines to use document field property "timestamp" "_timestamp": { "enabled": true, "path": "timestamp", "format": "yyyy/MM/dd HH:mm:ss" } > Time filter on Kibana causes no data to be displayed > ---------------------------------------------------- > > Key: RTGOV-428 > URL: https://issues.jboss.org/browse/RTGOV-428 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > Attachments: Screen Shot 2014-04-14 at 12.59.00.png > > > When setting the time filter, it causes no data to be displayed, even though there is data available for that time frame. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-428) Time filter on Kibana causes no data to be displayed

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-428?page=com.atlassian.jira.plugin.... ] Gary Brown commented on RTGOV-428: ---------------------------------- Just to clarify - are you saying that the Time Filter on the dashboard, which used @timestamp, should have worked ok - as the responsetime data's mapping identified the timestamp field in the data? If that is the case, then it appears that something is not working in kibana/elasticsearch, as the dashboard page had to be changed to explicitly using the 'timestamp' field before it would work correctly. > Time filter on Kibana causes no data to be displayed > ---------------------------------------------------- > > Key: RTGOV-428 > URL: https://issues.jboss.org/browse/RTGOV-428 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > When setting the time filter, it causes no data to be displayed, even though there is data available for that time frame. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-428) Time filter on Kibana causes no data to be displayed

by ivan mckinley (JIRA)

[ https://issues.jboss.org/browse/RTGOV-428?page=com.atlassian.jira.plugin.... ] ivan mckinley commented on RTGOV-428: ------------------------------------- This should be mapped accordingly in rtgov.mapping.json file. In general the document should define the timestamp field it should map to. This could be problematic for the object ActvitiyUnit as it does not expose a timestamp as a field so we automatically assign one on elasticsearch level. > Time filter on Kibana causes no data to be displayed > ---------------------------------------------------- > > Key: RTGOV-428 > URL: https://issues.jboss.org/browse/RTGOV-428 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > When setting the time filter, it causes no data to be displayed, even though there is data available for that time frame. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-428) Time filter on Kibana causes no data to be displayed

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-428?page=com.atlassian.jira.plugin.... ] Gary Brown resolved RTGOV-428. ------------------------------ Resolution: Done Issue was the time field being used by the time filter. > Time filter on Kibana causes no data to be displayed > ---------------------------------------------------- > > Key: RTGOV-428 > URL: https://issues.jboss.org/browse/RTGOV-428 > Project: RTGov (Run Time Governance) > Issue Type: Bug > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > > When setting the time filter, it causes no data to be displayed, even though there is data available for that time frame. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues April 2014