Editorial Guidelines
Please observe the following editorial guidelines when submitting blogs to APMdigest:
Getting Started
APMdigest recommends that you send an abstract or outline of your potential blog submission to Pete Goldin, Editor and Publisher of APMdigest, before you start writing the blog, to ensure it is something we would publish.
The following guidelines apply to non-vendors — such as analysts, consultants, integrators, authors and users — who would like to post a blog on APMdigest. Non-vendor blogs are posted in The APM Blog.
Companies or organizations that are not considered vendors include:
■ Analyst and research firms
■ Consultants
■ Integrators
■ Service providers that do not also sell their own products
■ Education, training and certification companies
■ Media
■ Authors
■ Government agencies
Vendor blogs are posted in the Vendor Forum. If you work for or represent a product vendor, and you want to submit a blog to APMdigest, click here for the Vendor Forum Guidelines.
Blogs from APMdigest sponsors are also posted in the Vendor Forum, but sponsors gain certain benefits when blogging. If you work for or represent a sponsor of APMdigest, click here for the Sponsor Blog Guidelines.
APMdigest only posts blogs from individuals who work for a company or organization in the IT market.
If you are a PR or Communications Manager or Agency, click here for some tips on how to interact with APMdigest.
If you are submitting a quote for an APMdigest list, such as our annual APM Predictions list, click here for guidelines.
Blog Guidelines
■ Your completed blog should be sent to the editor, when ready for posting. Word doc is the preferred format. APMdigest will post the blog under your byline.
■ APMdigest does not accept any blog submissions from gmail or other anonymous email accounts. You must send the blog from your corporate email account.
■ All blogs submitted to APMdigest must be original content that has not been published somewhere else. APMdigest periodically may request to re-post a blog, if the content is particularly valuable to our readers, but please do not pitch APMdigest to re-post your blog.
■ APMdigest does not accept blogs that are AI-generated. If APMdigest determines that it is highly likely a blog is AI-generated, it will not be posted.
■ Blogs should be objective, vendor-neutral, thought leadership pieces. Topics should be general industry interest to educate and enlighten our readers. Please do not promote your company, products, partners or any vendor in the blog copy or in related graphics submitted with the blog. When the blog is about solving issues relating to a specific environment or infrastructure brand, exceptions to this rule can be made on a case-by-case basis.
■ Do not mention any product brands or make negative references to a company, brand or product in any blogs on the Vendor Forum. The purpose of this rule is to prohibit vendors from posting negative blogs about their competitors. However,
■ If your blog is about a study, survey or report conducted or commissioned by your company, focus on the results of the survey/study. Do not focus on why and how the survey/study was conducted, or the value the report will have to readers.
■ Blogs do not have to follow AP style. They can be casual in style. However, APMdigest expects blogs to be written to meet basic grammar standards. If a blog does not meet these standards, this can significantly delay posting of the blog. Blogs that are well-written and ready for publishing will be posted first.
Word Count
Standard word count for a blog is 500-1000 words. This is not a strict rule. Word counts can be longer if the topic warrants more content. If your blog is longer than 1000 words, however, you may want to consider breaking it into multiple parts. Editorial decisions relating to word count are made on a case-by-case basis.
Deadline
APMdigest does not follow an editorial calendar, and usually does not assign a deadline. We post content as we receive it.
Publication Schedule
APMdigest posts one item of primary content — blog or feature — each day, Monday through Thursday. Consequently, there is often a queue of content waiting to be posted.
APMdigest does not post content on and around US holidays, including the week of July 4 and two weeks around Christmas/New Years.
APMdigest e-mails go out twice per month, and the current mailing includes content posted since the last mailing. During July and December, APMdigest may only send one email for that month.
Topics
Click here for a list of topics covered by APMdigest
If you are unsure whether your topic fits APMdigest, run your idea by Pete Goldin.
Author and Company Profile
If this is your first blog for APMdigest, send a one paragraph bio of the author and one paragraph profile of the company, along with the blog.
Related Links
On The APM Blog, non-vendor bloggers are welcome to include links at the end of the blog to link to their home page, or other relevant information such as research or events.
Hyperlinks in the body copy should be to support factual points you are making, or to link to your research referenced in the blog. However, non-vendor bloggers can also place a couple hyperlinks in the body copy of the blog linking to your company's web pages, if relevant.
Approval
All blogs will be reviewed by APMdigest prior to publication. APMdigest reserves the right to edit any content submitted, and the publication of any blog is at the sole discretion of APMdigest. Related links and hyperlinks included in the blog are also subject to APMdigest approval.
Reposting Blogs
If you contribute to APMdigest, you are free to re-post your own blog on your own website, as long as you mention that the blog was posted on APMdigest, and include a link to our site.
However, we recommend linking to the blog on APMdigest.com rather than posting the full blog on your site, to highlight the fact that the content was published by an independent third party. Publication of your blog on a respected industry site provides strong thought leadership credibility for the author and company.
The Latest
Traditional observability requires users to leap across different platforms or tools for metrics, logs, or traces and related issues manually, which is very time-consuming, so as to reasonably ascertain the root cause. Observability 2.0 fixes this by unifying all telemetry data, logs, metrics, and traces into a single, context-rich pipeline that flows into one smart platform. But this is far from just having a bunch of additional data; this data is actionable, predictive, and tied to revenue realization ...
64% of enterprise networking teams use internally developed software or scripts for network automation, but 61% of those teams spend six or more hours per week debugging and maintaining them, according to From Scripts to Platforms: Why Homegrown Tools Dominate Network Automation and How Vendors Can Help, my latest EMA report ...
Cloud computing has transformed how we build and scale software, but it has also quietly introduced one of the most persistent challenges in modern IT: cost visibility and control ... So why, after more than a decade of cloud adoption, are cloud costs still spiraling out of control? The answer lies not in tooling but in culture ...
CEOs are committed to advancing AI solutions across their organization even as they face challenges from accelerating technology adoption, according to the IBM CEO Study. The survey revealed that executive respondents expect the growth rate of AI investments to more than double in the next two years, and 61% confirm they are actively adopting AI agents today and preparing to implement them at scale ...
Image
A major architectural shift is underway across enterprise networks, according to a new global study from Cisco. As AI assistants, agents, and data-driven workloads reshape how work gets done, they're creating faster, more dynamic, more latency-sensitive, and more complex network traffic. Combined with the ubiquity of connected devices, 24/7 uptime demands, and intensifying security threats, these shifts are driving infrastructure to adapt and evolve ...
Image
The development of banking apps was supposed to provide users with convenience, control and piece of mind. However, for thousands of Halifax customers recently, a major mobile outage caused the exact opposite, leaving customers unable to check balances, or pay bills, sparking widespread frustration. This wasn't an isolated incident ... So why are these failures still happening? ...
Cyber threats are growing more sophisticated every day, and at their forefront are zero-day vulnerabilities. These elusive security gaps are exploited before a fix becomes available, making them among the most dangerous threats in today's digital landscape ... This guide will explore what these vulnerabilities are, how they work, why they pose such a significant threat, and how modern organizations can stay protected ...
The prevention of data center outages continues to be a strategic priority for data center owners and operators. Infrastructure equipment has improved, but the complexity of modern architectures and evolving external threats presents new risks that operators must actively manage, according to the Data Center Outage Analysis 2025 from Uptime Institute ...
As observability engineers, we navigate a sea of telemetry daily. We instrument our applications, configure collectors, and build dashboards, all in pursuit of understanding our complex distributed systems. Yet, amidst this flood of data, a critical question often remains unspoken, or at best, answered by gut feeling: "Is our telemetry actually good?" ... We're inviting you to participate in shaping a foundational element for better observability: the Instrumentation Score ...
We're inching ever closer toward a long-held goal: technology infrastructure that is so automated that it can protect itself. But as IT leaders aggressively employ automation across our enterprises, we need to continuously reassess what AI is ready to manage autonomously and what can not yet be trusted to algorithms ...