Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ability for timepicker to use aliases #72

Closed
tmkujala opened this issue May 8, 2013 · 3 comments
Closed

ability for timepicker to use aliases #72

tmkujala opened this issue May 8, 2013 · 3 comments

Comments

@tmkujala
Copy link

tmkujala commented May 8, 2013

Currently you must use an index pattern with the timepicker module, however the ability to use time-based aliases as well would be awesome.

@gurvindersingh
Copy link

+1

really required when using views for authorization for specific users

@gurvindersingh
Copy link

I have fixed this issue look it in to my fork of kibana and branch names aliases for it 👍

@rashidkpc
Copy link
Contributor

Implemented in pre3

spalger pushed a commit to spalger/kibana that referenced this issue Mar 3, 2016
spalger added a commit to spalger/kibana that referenced this issue Mar 3, 2016
add the cluster health API request params to KB
harper-carroll referenced this issue in harper-carroll/kibana Jul 11, 2016
Added a config for max file size on an individual pcap file
orouz added a commit to orouz/kibana that referenced this issue Jan 13, 2022
ari-aviran pushed a commit to ari-aviran/kibana that referenced this issue Feb 7, 2022
kqualters-elastic pushed a commit to kqualters-elastic/kibana that referenced this issue Mar 8, 2022
…seMode) functions. (elastic#72)

* more comments, improved isUserEntered function, as well as getChildren verbose filtering

* fixed tests. removed a test that wont be needed after verbose mode toggle is implemented.

Co-authored-by: mitodrummer <[email protected]>
rockdaboot pushed a commit that referenced this issue Jul 4, 2022
We had previously assumed that mget calls would always happen. However,
if there was no data from the initial search calls, then mget would not
be called, thus, the assertion failed.

Since we are making calls that return no data, I changed the assertion.
I also checked if response was valid (expected status code, expected
data type in the payload).
rockdaboot pushed a commit that referenced this issue Jul 4, 2022
We had previously assumed that mget calls would always happen. However,
if there was no data from the initial search calls, then mget would not
be called, thus, the assertion failed.

Since we are making calls that return no data, I changed the assertion.
I also checked if response was valid (expected status code, expected
data type in the payload).
rockdaboot pushed a commit that referenced this issue Jul 5, 2022
We had previously assumed that mget calls would always happen. However,
if there was no data from the initial search calls, then mget would not
be called, thus, the assertion failed.

Since we are making calls that return no data, I changed the assertion.
I also checked if response was valid (expected status code, expected
data type in the payload).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants