> For the complete documentation index, see [llms.txt](https://docs.monokot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.monokot.io/tags-and-devices/tags/tags-in-monokot-server-administrator/go-online.md).

# Go Online

For diagnostics (read) and debugging (write) tags Monokot Server Administrator provides the *Go Online* mode. In the *Go Online* mode, the following additional tag information is available:

* **Actual:** contains the converted value of the tag.
* **Raw:** contains the raw value of the tag (before conversion). If no value converter is set for the tag, the Actual and Raw fields are the same.
* **Status:** contains the current tag status, e.g. *Good*, *BadNoCommunication*, *BadLicenseExpired.*
* **Update Time:**  contains the time (UTC) of the last tag update.
* **Access**: contain access mode to tag.

To read and write the tag values, the following requirements must be met:

* The user (specified in the credentials for connection) must have the required access rights.
* The tag must exist on the server and have the required access rights.
* The tag must be associated with a device and have an address.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.monokot.io/tags-and-devices/tags/tags-in-monokot-server-administrator/go-online.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.