Feature: Metric for user scenario success / failure

[kubehe]

Please don't post questions here but use our community forum instead.

During load tests it would be great to have a OK/KO for single user scenario.
Currently there is granular per endpoint OK/KO, I'm missing full user journey metric to show management at which point users will be dissatisfied with our service.

[slandelle]

Sorry, I don't get it.

[slandelle]

During load tests it would be great to have a OK/KO for single user scenario.

@kubehe Could you please elaborate? I don't get if you're looking for metrics aggregated per scenario (available in Gatling Enterprise) or per user (which I'm not sure makes sense).

[kubehe]

At the time I was thinking about a metric similar to what a group gives you.

My main use case would be to calculate availability of the system for end user during load test.
It's hard to see flow conversion from simple metric like ratio of success to total requests.

Issues that I have with Group metric:

• You need to be explicit and remember to add it always to your scenario.
• There is no error list with failed assertions provided.

Simple example:

    final case class UserEnd(
        scenario: String,
        groupHierarchy: List[String],
        startTimestamp: Long,
        endTimestamp: Long,
        cumulatedResponseTime: Int,
        errorMessages: List[String]
        status: Status
    ) extends LoadEvent {
      val duration: Int = (endTimestamp - startTimestamp).toInt
    }

[Amerousful]

@kubehe
My 2 cents: You can create the rate metric based on a first and a last request in your scenario first request rps / last requets rps.

---

In: 100
Out: 100
Rate: 1

In: 100
Out: 50
Rate: 0.5 (something went wrong)