The authentication graphs break down the rates at which users and applications are authenticating to the GitHub Enterprise appliance. We also track the protocol or service type such as Git or API for the authentications, which is useful in identifying broad user activity trends. The authentication graphs can help find interesting trends or timeframes to look at when diving deeper into authentication and API request logs.
- Displays which methods users are authenticating with, and if they are successful in those attempts.
- Large numbers of failures usually indicate misconfigured clients which are failing repeatedly.
- Large numbers of authentications per second can cause authentication worker saturation.
- Automated requests or “polling” can be identified by a flat baseline, or intervals of authentications which occur regularly, even during off-peak times such as weekends or holidays.
- Human user authentication trends typically follow a bell curve, more closely matching your organization’s daily business hours.
LDAP graphs will only display data if LDAP Authentication is enabled on the GitHub Enterprise appliance. These graphs can help to identify slow responses from your LDAP server, as well as the overall volume of LDAP password based authentications.
- If any timeouts appear in the graph, GitHub Enterprise was unable to communicate with the LDAP server in time for an authentication request to take place.
- Failures indicate that users or clients are attempting to authenticate with an invalid LDAP username or password.
- Using a Personal Access Token authentication instead of username and password for users can help reduce the number and frequency of requests which rely on the LDAP server.
LDAP authentication response time
- Useful for tracking LDAP server performance trends, from the perspective of the GitHub Enterprise appliance.
- LDAP responses which take longer than 10 seconds will result in a timeout for the authentication request.
LDAP Sync Totals
- Reflects the number of
team, and net
new_membersrecords which were synchronized via the LDAP Synchronization feature, when the feature is enabled.
LDAP Sync Runtime
- If the runtime of team or user sync cycles exceeds the current LDAP Sync interval, the interval should be increased to allow completion before the next cycle.
- Long run times may indicate poor LDAP server performance, or suboptimal configuration of Domain Bases and restricted groups.
Continue the conversation
There’s more to come in the “Understanding your graphs” mini-series. If you’d like to follow along, just subscribe to the “Understanding your graphs” label (link below). Please let us know if you have any questions in the comments.