Added basic timestamp conversion support #181
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The issue this solution has is that it does not know the date format. While most user use ISO8601, it is possible to create a elasticsearch mapping where the stored value is something else, which will break the new Date(v). There would need to be some way to specify the format This is also changing the actual data in the set, instead of making it clear that only the presentation is being altered. Have you tested to be sure that clicking the search button on the timestamp field when expanding an event still functions as expected? I'd also like to see the timezone be configurable |
|
Great feedback! I'll work on getting some changes in that incorporate what you mentioned. Especially since the date searching is indeed broken with this patch. |
|
Are there any updates on this idea? |
|
Watching .... http://xkcd.com/1179/ |
|
Going to close this for now. |
spalger
pushed a commit
to spalger/kibana
that referenced
this pull request
Mar 3, 2016
- added a (temporary) cluster state event that ships the cluster state without the meta data section
- Updating files to comply with JSHint settings; Adding a way to fake the cluster data
- Adding react.js rendering to shard_allocation
- ClusterState Service & Additional Fixes
- Created ClusterState service
- Added EventEmitter2 Library
- Removed annimations from css (eating up too much cpu)
- Added option to hide header if embeded
- Reconfigured system to use update event from ClusterState to update
the visualiztion
- Refactored transformers to only use state
- Reordered nodes and indicies by name
- Add livereload to test:dev
- Add Angular-mocks to test framework
- Added getIndices method and tests
- Moved from state version to state @timestamp
- Cleaned up some potential issues with the $scope in changeData based
on errors I was seeing in the console.
- Adding player functionality
- Changed identifier for node to ip_port
- Collapse the timeline on nodes/indices dashboard
- Show hidden indices by default Fixes elastic#181
- Extend cover to show popover on wider portion of the timeline (to
cover the day markers)
- Lower case cluster health status in ClusterEvents
- Adding explain feature to cluster state
- Only displaying the difference of red vs. yellow indexes
- Renamed countByIndices to incrementIndexShardStatusCount
- Renamed getEndPoint to popFirstIndexAndReturnEndpoint
- Updated filterShards to only filter initializing shards that have
relocating_node set
- Refactored getTimelineData to use size/range for pagination
- Fixed typos
- Optimized the initial render so it does it once instead of twice from
the init() method and the $clusterState.$on('update')
- Changed all the panel variables to player variables
- Fix a bug with the fastForward feature
- Change Cluster Allocation to Shard Allocation
- Created a lightweight event bus
- Added mouseEnter and mouseLeave events to highlight corresponding
shards.
spalger
pushed a commit
to spalger/kibana
that referenced
this pull request
Mar 3, 2016
…anel The cluster panel's status now has an info icon to explain non-green state The indices stats table now takes index status into consideratio when choosing what indices to show. Indices stats table also sorts indices names with a .prefix lower then normal names. Closes elastic#143, Closes elastic#186, Relates to elastic#181
harper-carroll
pushed a commit
to harper-carroll/kibana
that referenced
this pull request
Jul 11, 2016
…ge-formats Added a new message type DataMsg; prototype protobuffer message to Stora...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should help fix #95
It's pretty basic, but:
So feel free to help clean it up a bit!