influxdb

Hi,

first thanks for this awesome software. But I have some trouble and I don't know how to proceed. First I try to find out what else I could provide for this report to be a good bug report.

First, I use the latest version (v1.14.0) from openSUSE build Service. I know, I should compile it by my self to avoid any other causes for this behavior. But for now I still use this package from there

It would be great if I could explore my data right after configuring it.

The current flow to look at data is:

1. Go to Datasources
2. Configure a datasource
3. Go back to Dashboards or Explore via sidemenu

The problem is that the configuration page offers only Save and Back as CTAs. Back only brings you back to the Datasources page. It would be great to have another button in addition t

Is your feature request related to a problem? Please describe.
So I'm working on a product that should allow schema-less ingestion out of the box. So my default ingestion method is via the influx line protocol.

But my challenge is that I also need to add indexes to some of the tags (symbols) after table creation. The problem is that the Influx Line protocol holds a lock to the table makin

Describe the bug

/usr/share/icinga2/include/command-plugins.conf provides the http CheckCommand. Since version 2.3.0 there is a new option in check_http which allows for checking the correctness of a certificate and hostname match: --verify-host. Please add this to the built in template library.

https://icinga.com/docs/icinga2/latest/doc/10-icinga-template-library/

$ /usr/

Hello David,

I have spent more than 20hours installing unpoller to Ubuntu 21.04 64bit. It seems that everything is working but Unpollen can not pick up settings from unpoller.conf file. Instead of that it is taking some default config file with URL https://127.0.0.1:8443: unifi controller. I have UDM Pro...

I have even try to set path with
docker run -v /home/ubuntu/Docker/unpoller:/config

When ockam-network/ockam#1756 lands, we will have TCP Transport Inlets and Outlets.

With that, it should be possible to build an example that does what ngrok does but using Ockam. I think a simple version of this should be possible in ~100 lines of Rust code, would be a really nice demo of how simple this is with Ockam.

The

A useful feature where the user specifies the quantity to take in an orderbook and callback returns the average price paid for that lot size. For example if the offers in the order book for BTC-USD was the following:

Price | size
11,000 | 1
10,500 | 1
10,000 | 1

If the user specified quantity 3, the callback would return 10,500.