add define for logs

README.md

@@ -2,7 +2,7 @@
 
 [![Build Status](https://jenkins.confdroid.com/buildStatus/icon?job=confdroid_alloy&style=plastic)](https://jenkins.confdroid.com/job/confdroid_alloy/)
 [![Security Hotspots](https://sonarqube.confdroid.com/api/project_badges/measure?project=confdroid_alloy&metric=security_hotspots&token=sqb_05c3bd9116b3d2585b1f06dd7b6d0d5a6433fe8b)](https://sonarqube.confdroid.com/dashboard?id=confdroid_alloy)
-[![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/grizzlycoda/puppet_collection)
+[![Ask DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/grizzlycoda/puppet_collection) 
 
 - [Readme](#readme)
   - [Synopsis](#synopsis)
@@ -55,6 +55,7 @@ See the full Puppet documentation including parameters in `docs/index.html`
 All dependencies must be included in the catalogue.
 
 - [confdroid_nagios](https://sourcecode.confdroid.com/confdroid/confdroid_nagios) if nagios monitoring is desired
+- [puppetlabs/concat](https://forge.puppet.com/modules/puppetlabs/concat) for composing the Alloy configuration
 
 ## Deployment
 
@@ -68,6 +69,15 @@ node 'example.example.net' {
 }
 ```
 
+External modules can add log files to Alloy's `path_targets` list with the
+`confdroid_alloy::log_targets` defined type:
+
+```puppet
+confdroid_alloy::log_targets { 'my_application':
+  targets => ['/var/log/my_application/*.log', '/var/log/my_application/audit.log'],
+}
+```
+
 - through Foreman:
 
 In order to apply parameters through Foreman, the params.pp must be added to the host or host group in question.