Not sure if I can help too much with this, a very basic set that crossed my mind without thinking too much about it: * Give me the path of the server log file * Give me the list of module dependencies of the deployment X * Give me the server launch command * Give me the server process ID * Give me the current server process status * Give me the JAVA OPTS used by the server * Give me the URL of the management console * Give me the current heap memory usage values * Tell me if the datasource X can get a connection In any case, something I think could be useful but not really related to the server management itself, could be to get a list of the RFEs developed for the current WildFly version and maybe provide a link to the corresponding WildFly proposal ... yes, you can achieve the same by going to the server release notes but maybe get them with a natural language would be useful without requiring to know from where this information can be got. The same applies to the CVEs resolved or affecting the current version Hope it helps. On Thu, Apr 3, 2025 at 12:19 AM Jean Francois Denise via wildfly-dev < wildfly-dev(a)lists.jboss.org&gt; wrote: > Hi, > I would need your help to collect questions that you would ask if you > were interacting in natural language with WildFly running servers. That is > going to help validate some tooling we are trying to put in place in the > WildFly MCP project (AI). > We have generated a lot of questions, but generation is ...generation and > lack of creativity... > We have also used LLM to generate questions but again the question we ask > to an LLM to generate a question is generated, so... > > Ideally 10 to 20 questions in your area of expertise, all bound to > WildFLy server (not the subsystem in extra feature-packs). > Some low level questions (not "please enable SSL for the management > interface"), quite focus, that you would use to retrieve the status of a > subsystem, an attribute, a child resource, ... We are currently not dealing > with updating the server state, just querying the state. > > If you plan to write down some questions, you are also strongly > encouraged to add a few (a few ;-)) crazy questions to make the system > crash! > > That would be great! > Thank-you. > JF > > Here are some basic examples that automation can generate: > * Can you get the information of the WildFly server? > * What is the valueof the system property foo? > * What is the server version? > * Can you resolve the ${JBOSS_HOME} expression? > * Can you get the path jboss.server.config.dir? > * Can you get the ExampleDS datasource? > * What are the files contained in the servlet-security.war deployment? > * Can you get the min-large-message-size attribute of the > myPooledConnectionFactory pooled-connection-factory resource of the > messaging-activemq subsystem ? > * Can you get the add component via interceptor attribute of the iiop > openjdk subsystem? > * Can you get all the file-handler resource of the logging subsystems? > * What is the value of the `caller-propagation` attribute for the > `iiop-openjdk` in the SAS context? > * What configuration option in the > microprofile-reactive-messaging-smallrye namespace is used to enable > OpenTelemetry tracing specifically for the Kafka connector? > _______________________________________________ > wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org > To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org > Privacy Statement: https://www.redhat.com/en/about/privacy-policy > List Archives: > https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message... > _______________________________________________ wildfly-dev mailing list -- wildfly-dev(a)lists.jboss.org To unsubscribe send an email to wildfly-dev-leave(a)lists.jboss.org Privacy Statement: https://www.redhat.com/en/about/privacy-policy List Archives: https://lists.jboss.org/archives/list/wildfly-dev@lists.jboss.org/message...