Elastic Search (ELK) components can consume and provide visibility to the data output by virtually any application. The configuration occurs within ELK, not inside DevTest. The configuration may also vary depending on the version of ELK components and the ELK deployment architecture.
If you are asking if CA provides documentation on configuring ELK to consume the DevTest log files (i.e., Logstash GROK filters and Kibana Dashboards for visualization), then the answer is no, not at this time.
Let's assume that you have a configuration where Filebeat sends DevTest log output to Logstash and Logstash performs GROK filtering and passes the output to Elastic Search.
In Filebeat, you need to configure the filebeat.yml to consume the DevTest log files, recognize multi-line output, and send the output to Logstash.
In Logstash, you need to configure the logstash.conf with various Grok patterns and pass the information to Elastic Search.
In Elastic Search, you need to create your filebeat index, set it to default if desired, and manage your data.
In Kibana, you query data and implement the visualizations.
The GROK filters will be the most complex part of the configuration. You will use a combination of OOTB GROK patterns and a few custom patterns. Might be a good idea to dump sample DevTest log output and feed it into one of the many online GROK tester applications.