grafana | source platform | Dashboard library

There's an instance of the grafana.ini file on the grafana host:

It depends on what you used for the $keyFile in your script.

A default name should be part of the /home/pi/.ssh/id_xxx names considered during an SSH session.
But a non-default name would need to be specified in an ~/.ssh/config: double-check if you have one.

Also, in your script, to be sure, don't use ~/.ssh, but /home/$USER/.ssh consistently, to avoid any mistake when the shell substitutes ~.

Prometheus doesn't implement it's own authentication|authorization.

Your best approach is to secure access to all host(s) running all software and, in this case, to the hosts running these Docker containers and all targets that you scrape etc.

All cloud providers provide ways by which you may limit access to the resources you create with their platforms. You'll want to become familiar with your preferred platforms' mechanisms and you should establish confidence, in part, by proving to yourself that you're able to restrict access to your services when you deploy then to these platforms.

Perhaps start with a simple test web site, secure it, then test that it is secure. Once you're confident in doing this, deploy your Prometheus services.

See this document on Prometheus security

Update:

I didn't find any way to get the number of rows through an API endpoint from Grafana, however, what I did was, I copied the Elasticsearch query that the Grafana dashboard made for the given panel in the dashboard [You can copy the query either by using Networks tab on Chrome, or, you can simply follow this:

• Get to this dropdown for panel:
• Press "Inspect"
• Click on "Query" tab here:
• There you will see the Query, copy it and use it in the Elasticsearch Query API, and you will get your desired JSON response ]

, and counted the number of "buckets" that are at the deepest level (say, you have used 4 group-by, example:

then the deepest bucket would be at level 4), and calculated the number of such Buckets which have keys, and that gives me the number of rows in the table panel.

This is a simple python code I wrote for the same:

There are a couple of important points to understand before getting started:

• When using the Artemis Prometheus Metrics Plugin neither the broker nor the applications "send" metrics to Prometheus. Prometheus itself must retrieve or "scrape" metrics from the broker. This is why the plugin comes with a servlet. The servlet exposes an HTTP endpoint that Prometheus can use to scrape metrics.
• The Artemis Prometheus Metrics Plugin is part of the broker infrastructure. It is not to be deployed as part of an application. The plugin's jar and war files are deployed on the broker and configured in broker.xml and bootstrap.xml respectively.

The Artemis Prometheus Metrics Plugin provides integration with Prometheus using two modules:

• artemis-prometheus-metrics-plugin: This provides the actual implementation of org.apache.activemq.artemis.core.server.metrics.ActiveMQMetricsPlugin and packages it with the Micrometer and Prometheus dependencies in an "uber" jar.

• artemis-prometheus-metrics-plugin-servlet: This provides a war file containing a simple servlet which can be deployed to the broker's embedded web server which then Prometheus can use to scrape metrics.

Once you clone the Artemis Prometheus Metrics Plugin repository simply run mvn install to build these two modules. The output will be in their respective target directories.

After building the modules follow these steps to deploy and configure the Artemis Prometheus Metrics Plugin. If you have some kind of dev-ops group which manages and configures your broker then they would follow these steps.

1. Copy artemis-prometheus-metrics-plugin/target/artemis-prometheus-metrics-plugin-.jar to /lib.

2. Add this to your /etc/broker.xml:

MongoDB is not supported currently. Only a certain set of DBs are supported.

Storage options in Loki

The following are supported for the index:

Single Store (boltdb-shipper) - Recommended for 2.0 and newer index store which stores boltdb index files in the object store

• Amazon DynamoDB
• Google Bigtable
• Apache Cassandra
• BoltDB (doesn’t work when clustering Loki)

The following are supported for the chunks:

• Amazon DynamoDB
• Google Bigtable
• Apache Cassandra
• Amazon S3
• Google Cloud Storage
• Filesystem

Grafana is just a visualisation tool. It needs a data source to query data and display. It is optimised for time series data, but static data can also be displayed easily.

Use the API plugin .

You can also use TestData DB data source which is available within Grafana to test scenarios. (does not use json though)

Once the data source is configured, you can use table panel to display data based on queries.

Each dashboard can have multiple panels so tables can be shown side by side.

count( col ) -- counts number of ROWS where col is not null. It's not about CH, it's ANSI SQL.

You actually should use countIf

In the documentation, this is written :

the address of a remote Elasticsearch server. When basic auth is needed, specify as: ://:@:. E.G., http://admin:pass@localhost:9200.

The documentation here : https://github.com/prometheus-community/elasticsearch_exporter#configuration

An example here : https://github.com/Lyr/ansible-elasticsearch-exporter/blob/master/templates/elasticsearch_exporter.service.j2