AutoCluster - Grafana dashboard isn't displaying Status Codes

[daveharris1]

The following issues has been raised after talking with Anton Moldovan.

NBomber NuGet package version: 5.6.0
NBomber.Sinks.InfluxDB NuGet package version: 5.0.2

When running distributed tests the Grafana dashboard 'Scenario Status Code' panel doesn't display any results.

The Grafana dashboard was created using the nbomber_board.json and nbomber_sessions_board.json found here:

https://github.com/PragmaticFlow/NBomber.Grafana

Sudo-code example of the code:

public async Task ApiResponseTimes(TestData testData)
        {
            var scenario = Scenario.Create("ApiResponseTimes", async context =>
            {
		//test logic
		var apiResponse = await AnApiCall(testData.Url).ConfigureAwait(false);		
		
		//Expect the Status code to be registered and displayed
                return Response.Ok(statusCode: apiResponse.StatusCode.ToString());
            })
            .WithRestartIterationOnFail(false)
            .WithoutWarmUp()
            .WithLoadSimulations(Simulation.KeepConstant(copies: testData.Copies, this.Duration));
            var nbomberRunner = NBomberRunner.RegisterScenarios(scenario)
                .WithLicense(await this.KeyVaultClient.GetSecretStringAsync(this.TestId, "NBomberKey").ConfigureAwait(false))
                .LoadConfig(await this.GenerateConfig().ConfigureAwait(false))
                .LoadInfraConfig(await this.GenerateInfraConfig().ConfigureAwait(false))
                .WithReportingSinks(this.influxDbSink)
                .Run();

[AntyaDev]

Hi @daveharris1

The StatusCode and Scenario Latency indicators will be displayed when the test status = complete. For "bombing" phase it's not display data.

[AntyaDev]

You can even find this information on the panel. There is a small button with a hint.

[daveharris1]

You can even find this information on the panel. There is a small button with a hint.

Thanks Anton. In our use case we have a number of StopWatches being used that determine when a distributed AutoCluster run should be stopped early via:

void StopCurrentTest(string reason);
(https://nbomber.com/docs/using-nbomber/basic-api/scenario/#scenario-context)

This means that the run ends in the following state of 'None':

Can we not have these HTTP statuses made available no matter what the state ends in?

[AntyaDev]

I think it's possible to overcome

[AntyaDev]

Fixed in NBomber 5.7.0-beta.7