# Adding Configuration files

**Configuration Directory Structure**

The `configurations` directory in the Git repository is intended for storing configuration files corresponding to supported agent types. When adding a new configuration file through the repository, it is important to follow the prescribed directory structure: 

```
<configurations>/
└── <agent_type>/
    └── <platform>/
        └── <name-of-configuration>/
            └── <path-to-configuration>/
                └── <config-file>
```

### Example: Grafana Alloy Configuration

```
configurations/
└── grafana-alloy/
    └── linux/
        └── default/
            └── etc/
                └── grafana-alloy/
                    └── config.alloy
```

In this example, `default` is the name of the configuration. The Grafana Alloy agent expects its configuration file to be at `/etc/grafana-alloy/config.alloy`, so the directory structure under `default/` mirrors this expected file path.

Following this structure ensures compatibility with automated deployment tools and consistent behavior across platforms.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.apica.io/fleet-management/fleet-config-repository/adding-configuration-files.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.