I have a Couch DB server that stores a number of sets of logs. Each of these is pulled into elastic search via a river. This works fine. Each of the indices has a timestamp field (the same field name in each index). I am trying to create a kibana dashboard which shows all a number of charts, one for each index. The problem I'm having is that there doesn't seem to be a way to distinguish which index each chart is built from. Is this possible or do I have to have a dashboard per index?
You can create custom dashboards depending upon the index. Create a new dashboard and visualize upon custom fields and add it to dashboard.
Likewise create new dashboard and you can add visualizations of another index.
Now you can monitor with different dashboards.
You may be able to use an alias that points to multiple indexes. Then create multiple queries.
Alias with multiple indices
Related
Is it possible to have data driven layout in Azure Workbooks?
For each row of a Kusto query, I'd like to add a tile to the dashboard.
There's no direct way to have a single query generate many visualizations in workbooks (yet!)
There are some options:
you could use a visualization like "tiles" which creates an item for each row, and you can configure the various parts of the tile to get info from different columns.
presuming you literally mean "Azure Dashboard" here when you say dashboard:
(more manual) you could create a parameter that returns all those values, and then configure a subsequent query to reference the selected value to generate the visualization you want, and manually pick a value, pin the chart to the dashboard, repeat for each value you want pinned.
(more technical) you could create the visualization you want, and pin it to a dashboard. then download the dashboard as json, and copy+paste the pin, but modify the query/parameter values in the dashboard, then upload it as a new dashboard?
Im trying to create a Unique sub list within a list in Sharepoint Online (2013).
I realize that sub lists arent exactly possible and you can use lookup fields to attach another list. This doesn't seem like it will work for my situation.
I am trying to have a list item that allows you to upload unique files per list item. For Example:
Reports May 2015
---School.xml
---Food.xml
Reports Jun 2016
---University.xml
---Beach.xml
Each list item will have a set of unique files related to it.The user needs to be able to make the List item themselves (Reports ... in this case), this will of course have other fields and descriptions attached to it (hence the list) and then be able to upload unique documents to that list item.
Im having problems figuring out how to do this in SharePoint. If there is another way to go about this better i am up for it.
You're right - sublists aren't a thing in SharePoint. Reading your requirements, I'm not sure if you need two lists to get what your looking for. Would it be possible to have a single Document Library with a custom field for "Category" or "Report Month". This field could either be a Single line of text field or Choice field. From there you could create a custom view to group by this field and give the hierarchical view from your example.
If you need separate metadata for the grouping/top level, you may need to use Lookups. If I was putting together the solution, I would set up a List and a corresponding Library with a Lookup field to the List. Each of the documents uploaded to the Library would reference the List via that Lookup. To provide an interface for interacting with both within the same view, you'd need to frontend it with some custom code such as a SharePoint-Hosted App.
I'm looking into using RedQueryBuilder for a web-based query builder. I want my users to be able to specify what data they want to retrieve in the select clause, but the demo site
only shows selecting a single table, rendering all the columns of that table in the result. Does RedQueryBuilder support building out a more robust select clause, like specifying which specific columns to retrieve including those joined from other tables?
I'm afraid not. The project just concentrates on defining a query to return rows not what to show in those rows.
The onTableChange callback would feed you the list of tables in the expression so could go from that to a list of available columns...
Would you want/need to alter the SQL query generated or just the display of the results?
Personally I'd be interested in changing the demo into a more useful query too although the scope of that could be huge.
I have two tables which both include a date field. Currently I have two portals, one for each table (occurrence).
Is it was possible to display the results of both of these in one portal, and sort by the date?
Technically a portal can only display records from one table. If you need to join two tables then you have to do this manually or change the design and use one table instead of two (since you want them in the same portal, then the tables are similar to some degree; maybe this similarity can go into its own table).
Sometimes developers use the so-called virtual table technique: they create a table with, say, a field with the record number and a bunch of calculated fields that pick their values from elsewhere, for example, from prefilled global variables. They create a portal to this table, set up the relationship to display the required number of records, and write the code to fill these variables. This way they can show data that isn't stored in any table, combine tables, etc. But it's an arcane technique, I would recommend it only as the last resort.
I have a WSS 3.0 site that I use for change management. There are three primary lists on it -- a bug list, an enhancement list, and a release list. The release list has two lookup columns that provide a list of bugs and enhancements that are included in that particular release.
I am trying to figure out how to filter the bug and enhancement list to include only items that have not already been included in another release. All the docs and examples I have seen regarding filtered lookups deal with a query on the list itself. For my situation, and if this was a SQL query, I would need to use a LEFT JOIN to generate the list.
To use SharePoint lists something like relational tables, you should try out SLAM (SharePoint list association manager), that is just what you need for this situation.
After you've set up your relations, you will then have a database you can use to query and determine if value has been used or not within your custom filtered lookup field.