> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/2-6-1/guides/system-connectivity/analytics-monitoring-alerting.md).

# Analytics, Monitoring & Alerting

Integration guides for analytics, monitoring, and alerting tools such as Grafana, Power BI, and Splunk.

These guides describe how to visualize shop floor data, ship metrics and logs to observability platforms, and turn machine events into alerts and tickets. The following guides are available:

| Guide                                                                                                                                               | Connector                                                         | Description                                                   |
| --------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------- | ------------------------------------------------------------- |
| [Grafana](/2-6-1/guides/system-connectivity/analytics-monitoring-alerting/grafana-integration.md)                                                   | [HTTP/REST](/2-6-1/connectors/enterprise-connectors/http-rest.md) | Post annotations and receive alert notifications via webhook. |
| [Power BI](/2-6-1/guides/system-connectivity/analytics-monitoring-alerting/power-bi-integration.md)                                                 | [HTTP/REST](/2-6-1/connectors/enterprise-connectors/http-rest.md) | Push live data to a streaming semantic model.                 |
| [Datadog](/2-6-1/guides/system-connectivity/analytics-monitoring-alerting/datadog-integration.md)                                                   | [HTTP/REST](/2-6-1/connectors/enterprise-connectors/http-rest.md) | Submit machine metrics and ship event logs.                   |
| [Splunk](/2-6-1/guides/system-connectivity/analytics-monitoring-alerting/splunk-integration.md)                                                     | [HTTP/REST](/2-6-1/connectors/enterprise-connectors/http-rest.md) | Stream events into a Splunk index via HTTP Event Collector.   |
| [ServiceNow](/2-6-1/guides/system-connectivity/analytics-monitoring-alerting/servicenow-integration.md)                                             | [HTTP/REST](/2-6-1/connectors/enterprise-connectors/http-rest.md) | Create incidents from alarms and poll assigned incidents.     |
| [Slack](/2-6-1/guides/system-connectivity/analytics-monitoring-alerting/slack-integration.md)                                                       | [HTTP/REST](/2-6-1/connectors/enterprise-connectors/http-rest.md) | Post machine alarms and production milestones to channels.    |
| [Docker Container Monitoring Using PRTG](/2-6-1/guides/system-connectivity/analytics-monitoring-alerting/docker-container-monitoring-using-prtg.md) | None                                                              | Monitor Connectware Docker containers with PRTG sensors.      |


---

# 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.cybus.io/2-6-1/guides/system-connectivity/analytics-monitoring-alerting.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.