How would I make stacked columns in this histogram #44
Comments
|
|
So there is no way to do it where I don't have to explicitly define each @fields.stack? Thats the hassle part. I could have LOTS. I am a recovering Splunk addict so I apologize in advance for my whining. |
|
And Thanks. David Winter | Director of Hosted Solutions On Apr 15, 2013, at 4:08 PM, dav3860 notifications@github.com wrote:
|
|
I've just added a feature request stating to use the result of a facet to populate the queries of a stacked histogram. |
|
Awesome. Thanks. Sent from my iPad On Apr 15, 2013, at 4:23 PM, dav3860 notifications@github.com wrote:
|
…e-with-service afsocket: Restore localport() support for network destinations
…l-panel Session detail panel
* Add comments * Add stricter typing * Collate stack frame metadata * Split grouping frames and creating a hash defaultGroupBy previously did both and now we have separate methods. * Decode file ID from base64 URL * Rename creation methods We use creation methods to construct instances of certain types. Sometimes these instances allow for no arguments, thus, the created instance is an instance with sensible defaults. To make the intent clearer for readers and also to adhere to the conventions used throughout the Kibana codebase, I renamed the creation methods to use 'create*' instead of 'build*'.
* Add comments * Add stricter typing * Collate stack frame metadata * Split grouping frames and creating a hash defaultGroupBy previously did both and now we have separate methods. * Decode file ID from base64 URL * Rename creation methods We use creation methods to construct instances of certain types. Sometimes these instances allow for no arguments, thus, the created instance is an instance with sensible defaults. To make the intent clearer for readers and also to adhere to the conventions used throughout the Kibana codebase, I renamed the creation methods to use 'create*' instead of 'build*'.
* Add comments * Add stricter typing * Collate stack frame metadata * Split grouping frames and creating a hash defaultGroupBy previously did both and now we have separate methods. * Decode file ID from base64 URL * Rename creation methods We use creation methods to construct instances of certain types. Sometimes these instances allow for no arguments, thus, the created instance is an instance with sensible defaults. To make the intent clearer for readers and also to adhere to the conventions used throughout the Kibana codebase, I renamed the creation methods to use 'create*' instead of 'build*'.
* Add comments * Add stricter typing * Collate stack frame metadata * Split grouping frames and creating a hash defaultGroupBy previously did both and now we have separate methods. * Decode file ID from base64 URL * Rename creation methods We use creation methods to construct instances of certain types. Sometimes these instances allow for no arguments, thus, the created instance is an instance with sensible defaults. To make the intent clearer for readers and also to adhere to the conventions used throughout the Kibana codebase, I renamed the creation methods to use 'create*' instead of 'build*'.
So that the stacked colors of the columns are the various fields in @fields.stack?
Thanks!
The text was updated successfully, but these errors were encountered: