[Feature Request] Provide a way to specify the useragent or at least a prefix

• Neo4j version: 3.5/4.0
• Driver version: master (and older)

newInstance calls createConnectionPool which calls ConnectionSettings(...) with no way to influence it.

There is a ConnectionSettings( AuthToken authToken, String userAgent, int connectTimeoutMillis ), but it isn’t called. And the useragent is final

• Expected behavior
• Actual behavior

Steps to reproduce

1. Start Neo4j
2. Start some connections to the database
3. Connect to the database using cypher-shell
4. run:

CALL dbms.listConnections() YIELD connectionId, connectTime, connector, username, userAgent, clientAddress;

Actual behavior

Note that all the useragents are neo4j-java/1.7.5... or neo4j-java/dev.

Expected behavior

Ideally, the useragent might be neo4j-java/dev cypher-shell/{version} or similar for the cyphershell connection, and the other ones should be able to identify themselves beyond “hi, I’m a driver”.

Once an API is available in the driver, the clients (e.g. cypher-shell) can be updated to use it…

[martin-neotech]

@jsoref https://neo4j.com/docs/api/java-driver/4.1/org/neo4j/driver/Config.ConfigBuilder.html#withUserAgent-java.lang.String-

[technige]

Hi @jsoref

The user-agent metadata is currently intended only for internal and informal use by the driver. As @zhenlineo mentions, this is not something we have ever surfaced for use by higher-level software or applications. It’s primary intended purpose is diagnostics.

I agree that the documentation in 12.5.1 is ambiguous, and this should make it clear that it is the driver version being reported, instead of simply saying “the software.” We will look to get that corrected.

In terms of introducing a way for higher-level software to be able to modify or extend the user agent, I have added the item to our roadmap for future discussion, so this may appear in a future release, depending on the outcome of that discussion.