You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -265,7 +265,7 @@ Hopsworks provides projects as a secure sandbox in which teams can collaborate a
265
265
Hopsworks provides a FTI (feature/training/inference) pipeline architecture for ML systems. Each part of the pipeline is defined in a Hopsworks job which corresponds to a Jupyter notebook, a python script or a jar. The production pipelines are then orchestrated with Airflow which is bundled in Hopsworks. Hopsworks provides several python environments that can be used and customized for each part of the FTI pipeline, for example switching between using PyTorch or TensorFlow in the training pipeline. You can train models on as many GPUs as are installed in a Hopsworks cluster and easily share them among users. You can also run Spark, Spark Streaming, or Flink programs on Hopsworks. JupyterLab is also bundled which can be used to run Python and Spark interactively.
266
266
267
267
## Available on any Platform
268
-
Hopsworks is available as a both managed platform in the cloud on AWS, Azure, and GCP, and can be installed on any Linux-based virtual machines (Ubuntu/Redhat compatible), even in air-gapped data centers. Hopsworks is also available as a serverless platform that manages and serves both your features and models.
268
+
Hopsworks is available to be installed on a kubernetes cluster in the cloud on AWS, Azure, and GCP, and On-Prem (Ubuntu/Redhat compatible), even in air-gapped data centers. Hopsworks is also available as a serverless platform that manages and serves both your features and models.
269
269
270
270
## Join the community
271
271
- Ask questions and give us feedback in the [Hopsworks Community](https://community.hopsworks.ai/)
@@ -34,27 +34,27 @@ button on the left side of the **email** row and fill out the form that pops up.
34
34
CRAM-MD5, LOGIN or PLAIN.
35
35
36
36
Optionally cluster wide Email alert receivers can be added in _Default receiver emails_.
37
-
These receivers will be available to all users when they create event triggered [alerts](../../user_guides/fs/feature_group/data_validation_best_practices#setup-alerts).
37
+
These receivers will be available to all users when they create event triggered [alerts](../../../user_guides/fs/feature_group/data_validation_best_practices#setup-alerts).
38
38
39
39
### Step 3: Configure Slack Alerts
40
40
Alerts can also be sent via Slack messages. To be able to send Slack messages you first need to configure
41
41
a Slack webhook. Click on the _Configure_ button on the left side of the **slack** row and past in your
42
42
[Slack webhook](https://api.slack.com/messaging/webhooks) in _Webhook_.
Optionally cluster wide Slack alert receivers can be added in _Slack channel/user_.
50
-
These receivers will be available to all users when they create event triggered [alerts](../../user_guides/fs/feature_group/data_validation_best_practices/#setup-alerts).
50
+
These receivers will be available to all users when they create event triggered [alerts](../../../user_guides/fs/feature_group/data_validation_best_practices/#setup-alerts).
51
51
52
52
### Step 4: Configure Pagerduty Alerts
53
53
Pagerduty is another way you can send alerts from Hopsworks. Click on the _Configure_ button on the left side of
54
54
the **pagerduty** row and fill out the form that pops up.
To test the alerts by creating triggers from Jobs and Feature group validations see [Alerts](../../user_guides/fs/feature_group/data_validation_best_practices/#setup-alerts).
96
+
To test the alerts by creating triggers from Jobs and Feature group validations see [Alerts](../../../user_guides/fs/feature_group/data_validation_best_practices/#setup-alerts).
97
97
98
98
The yaml syntax in the UI is slightly different in that it does not allow double quotes (it will ignore the values but give no error).
99
99
Below is an example configuration, that can be used in the UI, with both email and slack receivers configured for system alerts.
@@ -144,4 +144,4 @@ receivers:
144
144
```
145
145
146
146
## Conclusion
147
-
In this guide you learned how to configure alerts in Hopsworks.
147
+
In this guide you learned how to configure alerts in Hopsworks.
Copy file name to clipboardexpand all lines: docs/setup_installation/admin/audit/audit-logs.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ Audit logs can be configured from the _Cluster Settings_ Configuration tab.
17
17
You can access the _Configuration_ page of your Hopsworks cluster by clicking on your name, in the top right corner, and choosing _Cluster Settings_ from the dropdown menu.
Copy file name to clipboardexpand all lines: docs/setup_installation/admin/monitoring/grafana.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ You can access the admin page of your Hopsworks cluster by clicking on your name
17
17
You can then navigate to the _Monitoring_ tab. The _Monitoring_ tab gives you access to several of the observability tools that are already deployed to help you manage the health of the cluster.
@@ -36,7 +36,7 @@ Dashboards are organized into three folders:
36
36
-**Kubernetes**: If you have integrated Hopsworks with a Kubernetes cluster, this folder contains the dashboards to monitor the health of the Kubernetes cluster.
Copy file name to clipboardexpand all lines: docs/setup_installation/admin/monitoring/services-logs.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ You can access the admin page of your Hopsworks cluster by clicking on your name
17
17
You can then navigate to the _Monitoring_ tab. The _Monitoring_ tab gives you access to several of the observability tools that are already deployed to help you manage the health of the cluster.
@@ -32,7 +32,7 @@ You can filter the logs of a specific service by searching for the term `service
32
32
Currently only the logs of the following services are collected and indexed: Hopsworks web application (called `domain1` in the log entries), namenodes, resource managers, datanodes, nodemanagers, Kafka brokers, Hive services and RonDB. These are the core component of the platform, additional logs will be added in the future.
33
33
34
34
<figure>
35
-
<imgsrc="../../../assets/images/admin/monitoring/services_logs.png"alt="OpenSearch Dashboards with services logs" />
35
+
<imgsrc="../../../../assets/images/admin/monitoring/services_logs.png"alt="OpenSearch Dashboards with services logs" />
36
36
<figcaption>OpenSearch Dashboards displaying the logs</figcaption>
0 commit comments