opendistro-for-elasticsearch / kibana-visualizations Goto Github PK

It would be very useful to be able to add custom drilldowns to Kibana. There are a few examples of this via the elastic.co distribution and (not well-maintained) third-party plugins:

• elastic.co Kibana feature documentation (not open source)
• elastic.co github issue
• third-party plugin on github worked okay prior to new Kibana plugin architecture, hasn't been updated for a while

The feature would allow values to be used in creating URLs to other dashboards or external sources. For example, a dashboard developer could:

• generate a VirusTotal URL for a hash
• generate lookup URLs to iana.org for services, ports, protocols, mime-types, etc.
• generate links to issue ticketing systems, management tools, GitHub, etc.

This would allow a much greater degree of interoperability by allowing users to pivot to other tools from Kibana more easily.

We have several tenants for each of the several stages of each of our applications. We have also some standard dashboards which are automatically imported in each tenant of the application during deployment.

Each stage defines some index patterns like 'app-myapp--performance-*' which has a stage-neutral id (like 'performance-index'). This way the visualizations, saved searches etc. can be exported in dev-stage and then copied to the other tenants.

Unfortunately the TSVB references the index-patterns by name instead of id (as the other objects uses at our site).

eg. the tsvb (complete export below) references the index as
\"index_pattern\":\"app-myapp-dev-performance-*\"

while e.g the Metrics visualization references the index pattern by id as
"references":[{"id":"performance_index","name":"kibanaSavedObjectMeta.searchSourceJSON.index","type":"index-pattern"}

It would be great if this could be fixed as currently we have to modify these visualizations in each tenant

(we have currently opendistroforelasticsearch-kibana-1.11.0-1.x86_64)

here is the whole exported set if useful
{"attributes":{"description":"","kibanaSavedObjectMeta":{"searchSourceJSON":"{\"query\":{\"query\":\"\",\"language\":\"lucene\"},\"filter\":[]}"},"title":"Durchlaufzeiten pro Auftrag","uiStateJSON":"{}","version":1,"visState":"{\"type\":\"metrics\",\"aggs\":[],\"params\":{\"id\":\"61ca57f0-469d-11e7-af02-69e470af7417\",\"type\":\"metric\",\"series\":[{\"id\":\"61ca57f1-469d-11e7-af02-69e470af7417\",\"color\":\"#68BC00\",\"split_mode\":\"everything\",\"split_color_mode\":\"kibana\",\"metrics\":[{\"id\":\"61ca57f2-469d-11e7-af02-69e470af7417\",\"type\":\"min\",\"field\":\"json.inputreq.µs\"}],\"separate_axis\":0,\"axis_position\":\"right\",\"formatter\":\"us,ms,\",\"chart_type\":\"line\",\"line_width\":1,\"point_size\":1,\"fill\":0.5,\"stacked\":\"none\",\"label\":\"min. Zeit pro Auftrag\",\"type\":\"timeseries\",\"value_template\":\"{{value}} ms\",\"filter\":{\"query\":\"json.req.success: > 0\",\"language\":\"lucene\"}},{\"id\":\"2c830d10-cce3-11ea-b3b6-4774d5697189\",\"color\":\"#68BC00\",\"split_mode\":\"everything\",\"metrics\":[{\"id\":\"2c830d11-cce3-11ea-b3b6-4774d5697189\",\"type\":\"avg\",\"field\":\"json.inputreq.µs\"}],\"separate_axis\":0,\"axis_position\":\"right\",\"formatter\":\"us,ms,\",\"chart_type\":\"line\",\"line_width\":1,\"point_size\":1,\"fill\":0.5,\"stacked\":\"none\",\"label\":\"durchschn. Zeit pro Auftrag\",\"value_template\":\"{{value}} ms\",\"filter\":{\"query\":\"json.req.success: > 0\",\"language\":\"lucene\"}}],\"time_field\":\"json.@timestamp\",\"index_pattern\":\"app-myapp-dev-performance-*\",\"interval\":\"\",\"axis_position\":\"left\",\"axis_formatter\":\"number\",\"axis_scale\":\"normal\",\"show_legend\":1,\"show_grid\":1,\"default_index_pattern\":\"app-myapp-dev-app-*\",\"default_timefield\":\"json.@timestamp\",\"isModelInvalid\":false,\"background_color_rules\":[{\"id\":\"fa520a90-cce1-11ea-b3b6-4774d5697189\"}],\"drop_last_bucket\":1,\"ignore_global_filter\":0,\"bar_color_rules\":[{\"id\":\"49687880-cce2-11ea-b3b6-4774d5697189\"}],\"gauge_color_rules\":[{\"id\":\"4b5c8050-cce2-11ea-b3b6-4774d5697189\"}],\"gauge_width\":10,\"gauge_inner_width\":10,\"gauge_style\":\"half\",\"annotations\":[],\"time_range_mode\":\"entire_time_range\"},\"title\":\"Durchlaufzeiten pro Auftrag\"}"},"id":"eef0c360-cce3-11ea-95da-2574f2dbf7fc","migrationVersion":{"visualization":"7.8.0"},"references":[],"type":"visualization","updated_at":"2020-07-23T12:56:32.662Z","version":"WzEzMiwyXQ=="}

I'm using version 9.7.1 (aws elasticsearch domain with service software release number R20210331).

I tried to use a Gantt visualization using a dynamic field for the duration as:

I can see the field values in Discover tab, the diference in milliseconds, and I can also use the field in other visualizations.

But when I use it for the Duration field in Gantt visualization, the bars aren't shown.

If I use any other number field in the index, the bars are shown starting on the correct time:

I created then another Dynamic field concatenating two other string fields:

Again this field can be used everywhere but when used in the Gantt visualization:

Hello,

I have a dashboard, and using controls visualization on the dashboard. I am able to view and select the fields in my controls drop down, but when I apply the sections, those fields are not getting recognized by the global filter. Upon debugging further noticed that "Add Filter" link in the global filter is only allowing the fields that are part of my Default Index Pattern. When I change my default index to the index pattern used in my Controls visualization, then everything is working as expected. Is that a limitation or there is a hack to deal with the situation. My tenant is having so many index patterns, and this is becoming challenging when there are multiple dashboards using different index patterns.
Attaching screen below for your references.

Appreciate your help in this regard.

Thanks, Ravi Potnuru.

Hi Team ,

On the OD version [1.12.0] for the TSVB when I put for more than 3 days we are not able to see the date format on the tooltip below is the screenshot

When I increase the Time range for more than 7 days we are seeing the date format on the tooltip as below :

When I keep for 7 days and interval as 10m the tooltip is not working for that time range as well
interval 10m

interval 60m

For the interval 60m is fine but if we reduce the interval the tooltip is not showing
May I know is there any bug is raised for this or is there any changes need to get the tooltip correctly.

Kindly help me with this
Thanks
DILIP B K

I was excited to see gandtt charts added in the recent release.

Another great addition to the list of available visualizations would be a sankey diagram. Here are some references:

• Wikipedia
• Sankey diagrams in addition to Elastic.co's non-open-source Kibana in Vega
• Community plugin on GitHub (works up through Elastic 7.6.2 but not in new framework)

@anirudha, do you have examples of the Gantt charts this plugin is going to render?

I am working on a timeline chart at work using Vega and I'm planning to make a Kibana plugin out for it, but I would prefer using this Gantt chart instead if it meets my requirements.

Originally posted by @cascandaliato in opendistro-for-elasticsearch/sample-code#210 (comment)