diff --git a/content/en/blog/2025/otel-mainframe-priorities-survey.md b/content/en/blog/2025/otel-mainframe-priorities-survey.md
new file mode 100644
index 000000000000..ea71aed115f6
--- /dev/null
+++ b/content/en/blog/2025/otel-mainframe-priorities-survey.md
@@ -0,0 +1,68 @@
+---
+title: OpenTelemetry on Mainframe Priorities Survey
+linkTitle: Mainframe Priorities Survey
+date: 2025-01-31
+author: '[Ruediger Schulze](https://github.com/rrschulze) (IBM)'
+canonical_url: https://openmainframeproject.org/blog/opentelemetry-on-mainframe-priorities-survey/
+issue: https://github.com/open-telemetry/opentelemetry.io/issues/6045
+sig: SIG OpenTelemetry on Mainframe
+cSpell:ignore: Ruediger Schulze
+---
+
+The [OpenTelemetry](/) project and
+[The Open Mainframe Project](https://openmainframeproject.org/) established the
+[SIG “OpenTelemetry on Mainframe”](https://github.com/open-telemetry/sig-mainframe)
+at the beginning of 2024. Our focus is to enable OpenTelemetry on the mainframe
+for improved end-to-end observability and to support mainframe participation in
+hybrid cloud applications. **The SIG launched a new [survey] that calls for your
+participation.**
+
+## Background
+
+While there are many definitions of observability, we will refer here to the
+ability to receive actionable insight about the behavior of hybrid applications
+spanning multiple landing zones such as public and private cloud and mainframe
+environments.
+
+OpenTelemetry is a well-adopted open source framework for observability that
+aims to make high quality telemetry data such as traces, metrics, and logs
+available from any source to any target. OpenTelemetry remains the second most
+active project under the Cloud Native Computing Foundation (CNCF). The community
+of the OpenTelemetry project has made major efforts to provide specifications
+and implementations that unify the collection, processing, and distribution of
+telemetry.
+
+Given the breadth of the OpenTelemetry project and sophisticated capabilities of
+the mainframe, we as contributors to the SIG want to better understand the
+priorities for making the best use of OpenTelemetry on the mainframes. We seek
+feedback from a broad range of mainframe users and users of observability
+solutions, developers, site reliability engineers, application owners,
+architects, DevOps engineers, and all other experts in the field.
+
+The results of the [survey] will help us prioritize and implement targeted
+activities to accelerate the adoption of OpenTelemetry on the mainframe
+platform. Such activities could be the expedited porting of selected SDKs for
+code instrumentation to z/OS or the definition of Semantic Conventions for
+specific aspects of the platform. Once the survey is complete, we will publish
+the results and a prioritized list of activities on the websites of the
+OpenTelemetry project and The Open Mainframe Project.
+
+## Taking the survey
+
+The [survey] is structured in two sections. The first section gathers input
+about your role and background. The second section gathers the priorities of
+your organization for enabling OpenTelemetry on mainframes. Responding to the 20
+questions will take approximately 15 minutes. We appreciate your time spent on
+the survey and look forward to receiving your feedback!
+
+We invite you to take the [survey]. To learn more about the work of the
+OpenTelemetry on Mainframe SIG, join the conversation at
+[#otel-mainframes](https://cloud-native.slack.com/archives/C05PXDFTCPJ) on
+[CNCF Slack](https://slack.cncf.io/).
+
+_A version of this article was [originally posted] on the Open Mainframe Project
+blog._
+
+[originally posted]: {{% param canonical_url %}}
+
+[survey]: https://www.surveymonkey.com/r/HGTD2KJ
diff --git a/static/refcache.json b/static/refcache.json
index 17bb65c39678..622bd5b99a1d 100644
--- a/static/refcache.json
+++ b/static/refcache.json
@@ -1835,6 +1835,10 @@
     "StatusCode": 200,
     "LastSeen": "2024-08-09T10:45:38.976435-04:00"
   },
+  "https://cloud-native.slack.com/archives/C05PXDFTCPJ": {
+    "StatusCode": 200,
+    "LastSeen": "2025-01-29T09:52:40.815112084Z"
+  },
   "https://cloud-native.slack.com/archives/C076RUAGP37": {
     "StatusCode": 200,
     "LastSeen": "2024-08-20T08:40:41.563366481Z"
@@ -13247,6 +13251,10 @@
     "StatusCode": 206,
     "LastSeen": "2025-01-17T17:02:00.591524-05:00"
   },
+  "https://github.com/open-telemetry/sig-mainframe": {
+    "StatusCode": 206,
+    "LastSeen": "2025-01-29T09:52:33.855728393Z"
+  },
   "https://github.com/open-telemetry/sig-security": {
     "StatusCode": 200,
     "LastSeen": "2024-01-30T16:14:36.015951-05:00"
@@ -16035,6 +16043,14 @@
     "StatusCode": 200,
     "LastSeen": "2024-12-05T10:36:14.926178+01:00"
   },
+  "https://openmainframeproject.org/": {
+    "StatusCode": 200,
+    "LastSeen": "2025-01-29T09:52:30.138817065Z"
+  },
+  "https://openmainframeproject.org/blog/opentelemetry-on-mainframe-priorities-survey/": {
+    "StatusCode": 200,
+    "LastSeen": "2025-01-29T09:52:21.483732385Z"
+  },
   "https://openobserve.ai/docs/ingestion/logs/otlp/": {
     "StatusCode": 206,
     "LastSeen": "2024-08-09T10:45:10.679425-04:00"
@@ -20131,6 +20147,10 @@
     "StatusCode": 200,
     "LastSeen": "2024-10-09T10:19:40.728167+02:00"
   },
+  "https://www.surveymonkey.com/r/HGTD2KJ": {
+    "StatusCode": 200,
+    "LastSeen": "2025-01-29T09:52:38.143149632Z"
+  },
   "https://www.swift.org/": {
     "StatusCode": 206,
     "LastSeen": "2024-01-30T16:04:54.464334-05:00"