Grafana - The open-source platform for monitoring and observability

What is this feature?

This PR adds the code required to automatically create UI elements to match changes made in this alerting PR: https://github.com/grafana/alerting/pull/28

This adds UI elements to perform the following,

1. A checkbox to opt for basic auth.
2. A text field to supply the username
3. A dropdown to select a way to supply the password: The password can be entered in the UI or be supplied a file on the grafana server.
4. A dropdown to select the API version to use when publishing kafka messages.

Why do we need this feature?

1. Using this feature without auth is fine in simple projects but doesn't really work in larger companies.
2. The existing Kafka Contact Point only supported v2 APIs. While this was fine till now - newer systems are moving towards v3. Confluent is already only deploying v3 APIs for their Kafka Cloud Clusters.

Who is this feature for?

Anyone using the Kafka REST Contact Point with Grafana.

Which issue(s) does this PR fix?

Fixes https://github.com/grafana/grafana/issues/41176

Screenshots

The user can supply a password right here.

Or, they can choose to give a file path,

The user can select the desired API version like this,

References

Corresponding change in grafana/alerting: https://github.com/grafana/alerting/pull/28

Need help with

1. How do I make sure that this and the corresponding alerting changes go in together? If one goes in without the other, things might break. Do I wait for the alerting change to merge and then update the go.mod file to pick a newer version of the alerting package? Or is this somehow handled automatically?

Hello, in the docs it clearly states that Grafana alertmanager supports inhibition rules (see here) However I cannot find a single example or doc on how to actually configure inhibition in Grafana alertmanager. So what's going on here? can anyone give some info? is this even supported in Grafana alerting?

What is this feature?

Why do we need this feature?

Who is this feature for?

Which issue(s) does this PR fix?:

Fix corss build issue, setBuildEnv should be invoked before runPrint.

Before fix:

$ go run build.go --goos=darwin --goarch=amd64 build-server
Version: 9.4.0, Linux Version: 9.4.0, Package Iteration: 1673140414pre
rm -r dist
rm -r tmp
rm -r /Users/jimmiehan/go/pkg/darwin_amd64/github.com/grafana
building grafana-server ./pkg/cmd/grafana-server
rm -r ./bin/darwin-amd64/grafana-server
rm -r ./bin/darwin-amd64/grafana-server.md5
go build -ldflags -w -X main.version=9.4.0-pre -X main.commit=d44de7f20a -X main.buildstamp=1673058226 -X main.buildBranch=main -o ./bin/darwin-amd64/grafana-server ./pkg/cmd/grafana-server
go version
go version go1.19.1 darwin/arm64
Targeting darwin/amd64

$ file ./bin/darwin-amd64/grafana-server                                
./bin/darwin-amd64/grafana-server: Mach-O 64-bit executable arm64

After fix:

$ go run build.go --goos=darwin --goarch=amd64 build-server
Version: 9.4.0, Linux Version: 9.4.0, Package Iteration: 1673140473pre
rm -r dist
rm -r tmp
rm -r /Users/jimmiehan/go/pkg/darwin_amd64/github.com/grafana
building grafana-server ./pkg/cmd/grafana-server
rm -r ./bin/darwin-amd64/grafana-server
rm -r ./bin/darwin-amd64/grafana-server.md5
go build -ldflags -w -X main.version=9.4.0-pre -X main.commit=d1f213dcf2 -X main.buildstamp=1673097489 -X main.buildBranch=fix/jimmiehan-fix-cross-build -o ./bin/darwin-amd64/grafana-server ./pkg/cmd/grafana-server
go version
go version go1.19.1 darwin/arm64
Targeting darwin/amd64

$ file ./bin/darwin-amd64/grafana-server                   
./bin/darwin-amd64/grafana-server: Mach-O 64-bit executable x86_64

Special notes for your reviewer:

In line with issue #60570 which was closed without full investigation, if I create a panel using an MQTT data source and then change the panel I get an error message saying "Subscription to the channel 1/ds/LVo8dvh4z/1s/picow/temperature already exists". The MQTT source is a HiveMQ broker which is being connected to using tls. The panel works perfectly until a change is made to it, and then the error message appears.

The message can also be reproduced by deleting the panel and creating a new one with the same source.

What is this feature? In alerting we do some performance testing using the test data source with function RandomWalk. During investigating performance problems I found that the RandomWalk method was the bottleneck. This happens because it uses global randomizer instance, that has synchronous access guarded by a mutex.

This PR updates test data source to not use the global randomizer.