Best practices for large deployments in the Fleet Monitoring plugin - Fleet Monitoring 5.10.7.0

Security Center Fleet Monitoring Plugin Guide 5.10.8.0
Product
Fleet Monitoring
Content type
Guides > Plugin and extension guides
Version
5.10
Release
5.10.8.0
ft:locale
en-US
Last updated
2025-01-24

For larger fleets, typically made up of over 100 vehicles, you can optimize performance by configuring the frequency and volume of data offloads, the amount of data retained, and other Security Center features in use.

Best practices

General best practices
Category Details Reference
Database Use an independent database server for your large fleet deployment.

An independent database is required for failover, reduces load on the directory server, and helps with load balancing.

 Installing SQL Server independently of Security Center.
Installation order Install the independent SQL Server before installing the Security Center main server.

This order of installation prevents having to change database settings after the Security Center installation.

 Installing the Security Center main server.
Expansion servers Use expansion servers for failover directories, Fleet Monitoring plugins, Archiver roles, and Security Center Federation™ roles. An independent Directory database server is required for failover.

Fleet Monitoring plugin roles can support up to 500 vehicles.

 Installing Security Center expansion servers
Federation Use federation groups for every 100 federations. Expansion servers have a maximum of 5 federation groups. Requirements for large Federation systems
Failover directory Use a failover directory to perform load balancing on the directory and ensure high availability of the overall system.
NOTE: The failover directory can take over for the main directory if the main directory should fail or be taken down for upgrading.
 Directory failover and load balancing.
Server configuration Follow the best practices as provided in the Security Center documentation. Best practices for server configuration.
Fleet-specific best practices
Category Details Reference
Expansion servers Deploy each Fleet Monitoring plugin in its own expansion server. Best practices for server configuration.
Deployment Deploy all of your plugin instances in advance if possible. Deploying plugins in advance facilitates adding vehicles in any order because the desired plugin is always available for selection. Creating the Fleet Monitoring plugin role
Adding vehicles
  • Consider a logical way to group the vehicles and the number of vehicles per plugin when determining the number of Fleet Monitoring plugin instances for your system.
    Example: Group your vehicles by geographic region, transit type (bus, light rail, ferry), or even by vehicle identifiers.
  • Choose the correct host plugin to ensure that vehicle load is properly spread among the plugin instances.
 Adding AVL unit entities to Security Center