Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Total RPS Charts | Failures line chart does not display current number of failures #2469

Closed
2 tasks done
borget opened this issue Nov 16, 2023 · 3 comments · Fixed by #2471
Closed
2 tasks done

Total RPS Charts | Failures line chart does not display current number of failures #2469

borget opened this issue Nov 16, 2023 · 3 comments · Fixed by #2471
Labels

Comments

@borget
Copy link

borget commented Nov 16, 2023

Prerequisites

Description

The failures line chart does not show the current number of failures over time.

I have to refresh the page to get the line chart updated on the chart, The green RPS line does update and show up however the red line goes to 0 and it stays there.

  1. Opens the charts tab
  2. The next time the chart refreshes the failures line goes to zero and stays there

Screenshot 2023-11-16 at 17 23 00

  1. Refresh the page to see the failures.
  2. Red line goes to zero and stays there over time.
    Screenshot 2023-11-16 at 17 23 11

Command line

-f my_test.py --autostart --modern-ui

Locustfile contents

N/A

Python version

3.11

Locust version

2.18.3

Operating system

MacOS

@borget borget added the bug label Nov 16, 2023
@cyberw
Copy link
Collaborator

cyberw commented Nov 17, 2023

Ping @andrewbaldwin44

@andrewbaldwin44
Copy link
Collaborator

Hi @borget, I had the tests running for over ten minutes and I was not able to reproduce your issue. Could you please add some more information?

  • Are you able to reproduce this issue using the old UI?
  • If possible, could you include the contents of your locust file?

@borget
Copy link
Author

borget commented Nov 17, 2023

Hi @borget, I had the tests running for over ten minutes and I was not able to reproduce your issue. Could you please add some more information?

Hi @andrewbaldwin44,

Absolutely,

  • Are you able to reproduce this issue using the old UI?

No I am not, the issue is not present in the old UI when running the same test.

  • If possible, could you include the contents of your locust file?

Below relevant details about the locust file,

class FastUser(FastHttpUser):
    tasks = [FastUserTasks]


class FastUserTasks(TaskSet):
    @tag("Task1")
    @task(1)
    def task1(self):
        """
        I omitted how below variables are generated. Overall, there is some logic that generates protobuf messages
        that are sent as binary over http post action when executing the tasks, I have around 22 tasks that send 
        different protobuf messages.
        """
        self.client.post(
            url,
            name=f"/{message_type}",
            data=message,
            headers={
                "Content-Type": "application/octet-stream"
            }
        )

Please let me know if you need any extra information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants