What is the maximum number of users simultaneously login to Grafana for OSS latest version?

  • What Grafana version and what operating system are you using?
    latest version

  • What are you trying to achieve?
    Multi user access to the application

  • How are you trying to achieve it?
    Using open source version installed on Azure App service

  • What happened?
    Not able to handle more than 7 concurrent users

  • What did you expect to happen?
    There should not be any limit for concurrent user access

  • Can you copy/paste the configuration(s) that you are having problems with?

  • Did you receive any errors in the Grafana UI or in related logs? If so, please tell us exactly what they were.
    Username and Password incorrect

  • Did you follow any online instructions? If so, what is the URL?

Did you configure proper database for Grafana? Default sqlite is convenient for easy start, but it is file based and may have a problem with concurrent access.

Otherwise only used hardware is your limit.

ok thanks for the reply. I will check this , but as a production ready application can we go with default SQLite DB or shall replace it with postgresql DB?

That’s your call. Are you ready to loose Grafana DB? If yes, because you have everything automated and you can provision new Grafana instance and configs/dashboards in minute, then probably yes.

But that’s not a case for majority of Grafana deployements. Then you will benefit from serious DB (concurrent access, backup tools, replication).

1 Like

With SQLite, because of how the file-based database works, when you have lots of users you can run into issues where the database is both trying to read and write at the same time, and lock errors result. SQLite is a good easy option for starting out, but if you plan to have lots of users, a general database like mysql and postgresql is a better choice because they run many concurrent transactions and don’t have the file-based locking issue.

Generally with OSS Grafana we start out with sqlite because it’s so simple and doesn’t involve complex additional dependency setup when users are just getting started kicking the tires.

You can read more about the file based locking issue here. Some possibly useful tools/instructions for migrating to postgresql can be found here

1 Like

thanks a lot for providing quick support.