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
Copy file name to clipboardExpand all lines: ha-dr.md
+5-3
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
---
2
2
3
3
copyright:
4
-
years: 2023
5
-
lastupdated: "2023-02-21"
4
+
years: 2024
5
+
lastupdated: "2024-02-09"
6
6
7
7
keywords: HA for Code Engine, DR for Code Engine, high availability for Code Engine, disaster recovery for Code Engine, failover for Code Engine, backing up code engine, availability of code engine, code engine regions, backing up your Code Engine instance
8
8
@@ -30,7 +30,8 @@ The following table lists the high-availability (HA) status for the regions (loc
30
30
| Asia Pacific | Australia (`au-syd`) | MZR |
31
31
| Asia Pacific | Osaka (`jp-osa`) | MZR |
32
32
| Asia Pacific | Tokyo (`jp-tok`) | MZR |
33
-
| Europe | Frankfurt (`eu-de`) | MZR |
33
+
| Europe | Frankfurt (`eu-de`) | MZR |
34
+
| Europe | Madrid (`eu-es`) | MZR |
34
35
| Europe | London (`eu-gb`) | MZR |
35
36
| North America | Dallas (`us-south`) | MZR |
36
37
| North America | Toronto (`ca-tor`) | MZR |
@@ -65,6 +66,7 @@ In a major regional disaster, such as an earthquake, flood, or tornado, an entir
Copy file name to clipboardExpand all lines: logging.md
+9-9
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
copyright:
4
4
years: 2020, 2024
5
-
lastupdated: "2024-01-25"
5
+
lastupdated: "2024-02-08"
6
6
7
7
keywords: logging for code engine, logs for code engine, job logs for code engine, app logs for code engine, build logs for code engine, logs
8
8
@@ -66,13 +66,13 @@ For more information about configuring and starting logging in the console, see
66
66
#### What if my log data is multi-line?
67
67
{: #view-logs-multiline}
68
68
69
-
Every log line must contain log level and timestamp information to appear correctly in {{site.data.keyword.la_full_notm}}. If your log lines span multiple lines, change how you format and output your logs so that they are in a single line. Use JSONL format for your logs with {{site.data.keyword.la_full_notm}}. Your logs must also
69
+
Every log line must contain log level and timestamp information to appear correctly in {{site.data.keyword.la_full_notm}}. If your log lines span multiple lines, change how you format and output your logs so that they are in a single line. Use the JSONL format for your logs with {{site.data.keyword.la_full_notm}}. Your logs must also
70
70
conform to [limits for {{site.data.keyword.la_full_notm}} logs](/docs/log-analysis?topic=log-analysis-ingest_limits). After you make log formatting changes, you can take advantage of {{site.data.keyword.la_full_notm}} search and formatting features.
71
71
72
72
### Viewing app logs from the console
73
73
{: #view-applogs-ui}
74
74
75
-
After you select the project that you want to work with, you can add logging capabilities from the {{site.data.keyword.codeengineshort}} Overview page, or one of its subpages such as the Applications page, or from the page that is specific to your application. The following steps assume that you are working from a specific {{site.data.keyword.codeengineshort}} application page.
75
+
After you select the project that you want to work with, you can add logging capabilities from the {{site.data.keyword.codeengineshort}} Overview page or one of its child pages such as the Applications page, or from the page that is specific to your application. The following steps assume that you are working from a specific {{site.data.keyword.codeengineshort}} application page.
76
76
{: note}
77
77
78
78
1. Go to an app that you created and deployed. From the [Projects page on the {{site.data.keyword.codeengineshort}} console](https://cloud.ibm.com/codeengine/projects){: external}, select your project and then select **Applications**. Select the app that you want to work with.
@@ -91,26 +91,26 @@ Alternatively, you can configure a {{site.data.keyword.la_short}} instance by us
91
91
### Viewing job logs from the console
92
92
{: #view-joblogs-ui}
93
93
94
-
After you select the project that you want to work with, you can add logging capabilities from the {{site.data.keyword.codeengineshort}} Overview page, or one of its subpages such as the Jobs page, or from the page that is specific to your job. The following steps assume that you are working from a specific {{site.data.keyword.codeengineshort}} job page.
94
+
After you select the project that you want to work with, you can add logging capabilities from the {{site.data.keyword.codeengineshort}} Overview page or one of its child pages such as the Jobs page, or from the page that is specific to your job. The following steps assume that you are working from a specific {{site.data.keyword.codeengineshort}} job page.
95
95
{: note}
96
96
97
97
1. Navigate to a job that you created and deployed. From the [Projects page on the {{site.data.keyword.codeengineshort}} console](https://cloud.ibm.com/codeengine/projects){: external}, select your project and then select **Jobs**. Select the job that you want to work with.
98
98
2. From your {{site.data.keyword.codeengineshort}} job page, you can add logging capabilities. If you have previously created a {{site.data.keyword.la_short}} instance, click **Logging**, and this action opens the {{site.data.keyword.la_short}} service. Else, complete the following steps to configure logging capabilities.
99
99
1. From the **Submit job** options menu, click **Add logging** to create the {{site.data.keyword.la_full_notm}} instance. This action opens the {{site.data.keyword.la_short}} service.
100
100
2. From the {{site.data.keyword.la_short}} service, create your logging instance. To confirm that your logging instance is created, check the [Observability dashboard](https://cloud.ibm.com/observe/logging).
101
101
3. From your {{site.data.keyword.codeengineshort}} job page, click **Add logging** from the **Submit job** options menu. This time, select a {{site.data.keyword.la_short}} instance to receive platform logs. Choose the logging instance that you created in the prior step. Click **Select**. {{site.data.keyword.codeengineshort}} requires enabled platform logs to receive {{site.data.keyword.codeengineshort}} logging data. When you complete this action, {{site.data.keyword.codeengineshort}} enables platform logging for you.
102
-
3. Now that platform logging is configured, from your {{site.data.keyword.codeengineshort}} job page, click **Logging** from the **Submit job** options menu to open your platform logs window. Be sure to keep this platform logs window open to receive your logging data if you are using the {{site.data.keyword.la_short}} free tier. Don't keep this window open if you are using a {{site.data.keyword.la_short}} paid tier.
103
-
4. (optional) Refine the [filter for your search](#view-logs-filters), if needed.
104
-
5. Run your job. From the **Job runs** area, click **Submit job** to run your job. Provide the job run configuration values or you can take the default values. Click **Submit job** to run your job. You can view platform logs from the job run in the platform logs window.
102
+
3. Now that platform logging is configured, from your {{site.data.keyword.codeengineshort}} job page, click **Logging** from the **Submit job** options menu to open your platform logs window. Be sure to keep this platform logs window open to receive your logging data if you are using the {{site.data.keyword.la_short}} free tier. Don't keep this window open if you are using a {{site.data.keyword.la_short}} paid tier.
103
+
4. (optional) Refine the [filter for your search](#view-logs-filters), if needed.
104
+
5. Run your job. From the **Job runs** area, click **Submit job** to run your job. Provide the job run configuration values or you can take the default values. Click **Submit job** to run your job. You can view platform logs from the job run in the platform logs window.
105
105
106
106
Your {{site.data.keyword.la_short}} instance is now configured such that it can receive platform logging for your {{site.data.keyword.codeengineshort}} job.
107
107
108
-
Alternatively, you can configure a {{site.data.keyword.la_short}} instance by using the [Observability dashboard](https://cloud.ibm.com/observe/logging) to create the instance, and then by [configuring platform logs](/docs/log-analysis?topic=log-analysis-config_svc_logs&interface=ui#config_svc_logs_ui). After you create your instance, click **Configure platform logs**. Select the {{site.data.keyword.la_short}} instance to receive the platform log data by specifying a region and your log instance.
108
+
Alternatively, you can configure a {{site.data.keyword.la_short}} instance by using the [Observability dashboard](https://cloud.ibm.com/observe/logging) to create the instance, and then by [configuring platform logs](/docs/log-analysis?topic=log-analysis-config_svc_logs&interface=ui#config_svc_logs_ui). After you create your instance, click **Configure platform logs**. Select the {{site.data.keyword.la_short}} instance to receive the platform log data by specifying a region and your log instance.
109
109
110
110
### Viewing function logs from the console
111
111
{: #view-funlogs-ui}
112
112
113
-
After you select the project that you want to work with, you can add logging capabilities from the {{site.data.keyword.codeengineshort}} Overview page, or one of its subpages such as the Functions page, or from the page that is specific to your function. The following steps assume that you are working from a specific {{site.data.keyword.codeengineshort}} function page.
113
+
After you select the project that you want to work with, you can add logging capabilities from the {{site.data.keyword.codeengineshort}} Overview page or one of its child pages such as the Functions page, or from the page that is specific to your function. The following steps assume that you are working from a specific {{site.data.keyword.codeengineshort}} function page.
114
114
{: note}
115
115
116
116
1. Go to a function that you created and deployed. From the [Projects page on the {{site.data.keyword.codeengineshort}} console](https://cloud.ibm.com/codeengine/projects){: external}, select your project and then select **Functions**. Select the function that you want to work with.
Copy file name to clipboardExpand all lines: regions.md
+5-2
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
---
2
2
3
3
copyright:
4
-
years: 2023
5
-
lastupdated: "2023-06-13"
4
+
years: 2024
5
+
lastupdated: "2024-02-09"
6
6
7
7
keywords: regions for code engine, target region for code engine, endpoints for code engine, api endpoints in code engine, regions, endpoints
8
8
@@ -27,6 +27,7 @@ subcollection: codeengine
27
27
- Asia Pacific: Tokyo, Japan (`jp-tok`) region
28
28
- Europe: Germany (`eu-de`) region
29
29
- Europe: Great Britain (`eu-gb`) region
30
+
- Europe: Spain (`eu-es`) region
30
31
31
32
You can target a specific region whenever you log in to the {{site.data.keyword.cloud_notm}} CLI or change your current region by using the [`target -r`](/docs/cli?topic=cli-ibmcloud_cli#ibmcloud_target) option.
32
33
@@ -59,6 +60,7 @@ Use the following endpoints to access and manage project resources.
59
60
| Asia Pacific: Tokyo, Japan |`api.jp-tok.codeengine.cloud.ibm.com`|`api.private.jp-tok.codeengine.cloud.ibm.com`|
Copy file name to clipboardExpand all lines: release-notes.md
+9-1
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
copyright:
4
4
years: 2020, 2024
5
-
lastupdated: "2024-02-06"
5
+
lastupdated: "2024-02-09"
6
6
7
7
keywords: release notes for code engine, updates in code engine, what's new in code engine, document changes in code engine, updates, release notes
8
8
@@ -23,6 +23,14 @@ Use the release notes to learn about the latest changes to {{site.data.keyword.c
23
23
## February 2024
24
24
{: #codeengine-feb24}
25
25
26
+
### 09 February 2024
27
+
{: #codeengine-feb0924}
28
+
{: release-note}
29
+
30
+
New region!
31
+
: {{site.data.keyword.codeengineshort}} is supported in a new region: Madrid, Spain (`eu-es`). See [Regions for {{site.data.keyword.codeengineshort}}](/docs/codeengine?topic=codeengine-regions).
0 commit comments