> For the complete documentation index, see [llms.txt](https://docs.islandrouter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.islandrouter.com/island-router-cli-2.3.2/commands/history/history-url.md).

# history url

Specifies a remote directory to which history files will be written.

## Syntax

```
[no] history <instance> url [<url>]
```

## Syntax Description

<table><thead><tr><th width="203">Keyword</th><th>Description</th></tr></thead><tbody><tr><td><code>no</code></td><td>Removes the specified history URL.</td></tr><tr><td>instance</td><td>The history instance to be modified. If the specified instance does not exist, it will be created unless the no keyword was also specified. Must be alphanumeric.</td></tr><tr><td>url</td><td>This URL to which history files are to be written. Required unless the <code>no</code> parameter is specified.</td></tr></tbody></table>

## Defaults

The default is to not write history files to a remote system

## Usage Guidelines

This command specifies the destination for files produced for this history instance.

The URL must point to a remote directory. Each history file will be writton to a unique file in that directory. The file name format is:

`history.YYYYMMDDHHMMSSmmm‐nnnnnnnnnn`

where “YYYYMMDDHHMMSSmmm” is the date and time including milliseconds and “nnnnnnnnnn” is the number of records in the file.

The path portion of the URL is ignored for the "tcp\://" or "udp\://" real-time streaming schemes.

Refer to the [URL Format](https://docs.islandrouter.com/island-router-cli-2.3.2/url-format.md) section of this document for more information on the syntax of the url parameter.

## Examples

```
history myhist3 url scp://jane:d9fzC@10.14.2.7/history
```

## Related Commands


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.islandrouter.com/island-router-cli-2.3.2/commands/history/history-url.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
