Grafana

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

This is kind of a follow up to #32677 and the PR #34762.

In #34762 we improved the test data source implementation by checking the body of the response from Tempo. The Tempo team is not comfortable making the body of a 404 response part of our stable API, so instead we are currently adding a separate endpoint specifically for testing: /api/echo (grafana/tempo#714).

https://github.com/heptiolabs/healthcheck

This will give us metric on healtcheck and more granularity on checks we want to have.

/cc @slim-bean @joe-elliott

Scenario

create table tab(f float);
insert into tab(f) values(4273.8);

Results in: org.postgresql.util.PSQLException: ERROR: inconvertible types: DOUBLE -> FLOAT [from=4273.8, to=f]

Expectation

Possibly enhance type compatibility check (SqlCompiler.isAssignableFrom) with extra cases for numeric types:

• Float <- Double: if the double fits in the Float, then

Add following Contents to Cloud Providers - https://github.com/Tikam02/DevOps-Guide/tree/master/Cloud_providers

• Add basic concepts of following providers:
  • AWS
  • GCP
  • Azure
• Add tips & tricks
• Add commands

Describe the bug

When entering a cost per kWh in the charge-cost page, I need to use 4 decimal places as my supplier charges in fractions of cents. For example, if I enter 0.1446, it responds with:
`Please enter a valid value. The

Describe the bug
I copy-pasted a trace ID and added a space at the end by accident.
The resulting error was:

failed to get trace with id: 1f34e43692d1f5d8 Status: 400 Bad Request Body: encoding/hex: invalid byte: U+0020 ' '

This error is quite difficult to understand, and also not helpful in pointing out the problem.

Expected behavior
Something like this would be easier

Currently in beta
https://grafana.com/docs/grafana/latest/panels/visualizations/pie-chart-panel/