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
Most organizations approach OpenTelemetry as a collection of individual tools they need to assemble from scratch. This view misses the bigger picture. OpenTelemetry is a complete telemetry framework with composable components that address specific problems at different stages of organizational maturity. You start with what you need today and adopt additional pieces as your observability practices evolve ...
One of the earliest lessons I learned from architecting throughput-heavy services is that simplicity wins repeatedly: fewer moving parts, loosely coupled execution (fewer synchronous calls), and precise timing metering. You want data and decisions to travel the shortest possible path. The goal is to build a system where every strategy and each line of code (contention is the key metric) complements the decision trees ...
As discussions around AI "autonomous coworkers" accelerate, many industry projections assume that agents will soon operate alongside human staff in making decisions, taking actions, and managing tasks with minimal oversight. But a growing number of critics (including some of the developers building these systems) argue that the industry still has a long way to go to be able to treat AI agents like fully trusted teammates ...
Enterprise AI has entered a transformational phase where, according to Digitate's recently released survey, Agentic AI and the Future of Enterprise IT, companies are moving beyond traditional automation toward Agentic AI systems designed to reason, adapt, and collaborate alongside human teams ...
The numbers back this urgency up. A recent Zapier survey shows that 92% of enterprises now treat AI as a top priority. Leaders want it, and teams are clamoring for it. But if you look closer at the operations of these companies, you see a different picture. The rollout is slow. The results are often delayed. There's a disconnect between what leaders want and what their technical infrastructure can handle ...
Kyndryl's 2025 Readiness Report revealed that 61% of global business and technology leaders report increasing pressure from boards and regulators to prove AI's ROI. As the technology evolves and expectations continue to rise, leaders are compelled to generate and prove impact before scaling further. This will lead to a decisive turning point in 2026 ...
Cloudflare's disruption illustrates how quickly a single provider's issue cascades into widespread exposure. Many organizations don't fully realize how tightly their systems are coupled to third party services, or how quickly availability and security concerns align when those services falter ... You can't avoid these dependencies, but you can understand them ...
If you work with AI, you know this story. A model performs during testing, looks great in early reviews, works perfectly in production and then slowly loses relevance after operating for a while. Everything on the surface looks perfect — pipelines are running, predictions or recommendations are error-free, data quality checks show green; yet outcomes don't meet the ground reality. This pattern often repeats across enterprise AI programs. Take for example, a mid-sized retail banking and wealth-management firm with heavy investments in AI-powered risk analytics, fraud detection and personalized credit-decisioning systems. The model worked well for a while, but transactions increased, so did false positives by 18% ...
Basic uptime is no longer the gold standard. By 2026, network monitoring must do more than report status, it must explain performance in a hybrid-first world. Networks are no longer just static support systems; they are agile, distributed architectures that sit at the very heart of the customer experience and the business outcomes ... The following five trends represent the new standard for network health, providing a blueprint for teams to move from reactive troubleshooting to a proactive, integrated future ...
APMdigest's Predictions Series concludes with 2026 AI Predictions — industry experts offer predictions on how AI and related technologies will evolve and impact business in 2026. Part 5, the final installment, covers AI's impacts on IT teams ...