Skip to main content

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

People want to be doing more engaging work, yet their day often gets overrun by addressing urgent IT tickets. But thanks to advances in AI "vibe coding," where a user describes what they want in plain English and the AI turns it into working code, IT teams can automate ticketing workflows and offload much of that work. Password resets that used to take 5 minutes per request now get resolved automatically ...

Governments and social platforms face an escalating challenge: hyperrealistic synthetic media now spreads faster than legacy moderation systems can react. From pandemic-related conspiracies to manipulated election content, disinformation has moved beyond "false text" into the realm of convincing audiovisual deception ...

Traditional monitoring often stops at uptime and server health without any integrated insights. Cross-platform observability covers not just infrastructure telemetry but also client-side behavior, distributed service interactions, and the contextual data that connects them. Emerging technologies like OpenTelemetry, eBPF, and AI-driven anomaly detection have made this vision more achievable, but only if organizations ground their observability strategy in well-defined pillars. Here are the five foundational pillars of cross-platform observability that modern engineering teams should focus on for seamless platform performance ...

For all the attention AI receives in corporate slide decks and strategic roadmaps, many businesses are struggling to translate that ambition into something that holds up at scale. At least, that's the picture that emerged from a recent Forrester study commissioned by Tines ...

From smart factories and autonomous vehicles to real-time analytics and intelligent building systems, the demand for instant, local data processing is exploding. To meet these needs, organizations are leaning into edge computing. The promise? Faster performance, reduced latency and less strain on centralized infrastructure. But there's a catch: Not every network is ready to support edge deployments ...

Every digital customer interaction, every cloud deployment, and every AI model depends on the same foundation: the ability to see, understand, and act on data in real time ... Recent data from Splunk confirms that 74% of the business leaders believe observability is essential to monitoring critical business processes, and 66% feel it's key to understanding user journeys. Because while the unknown is inevitable, observability makes it manageable. Let's explore why ...

Organizations that perform regular audits and assessments of AI system performance and compliance are over three times more likely to achieve high GenAI value than organizations that do not, according to a survey by Gartner ...

Kubernetes has become the backbone of cloud infrastructure, but it's also one of its biggest cost drivers. Recent research shows that 98% of senior IT leaders say Kubernetes now drives cloud spend, yet 91% still can't optimize it effectively. After years of adoption, most organizations have moved past discovery. They know container sprawl, idle resources and reactive scaling inflate costs. What they don't know is how to fix it ...

Artificial intelligence is no longer a future investment. It's already embedded in how we work — whether through copilots in productivity apps, real-time transcription tools in meetings, or machine learning models fueling analytics and personalization. But while enterprise adoption accelerates, there's one critical area many leaders have yet to examine: Can your network actually support AI at the speed your users expect? ...

The more technology businesses invest in, the more potential attack surfaces they have that can be exploited. Without the right continuity plans in place, the disruptions caused by these attacks can bring operations to a standstill and cause irreparable damage to an organization. It's essential to take the time now to ensure your business has the right tools, processes, and recovery initiatives in place to weather any type of IT disaster that comes up. Here are some effective strategies you can follow to achieve this ...

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

People want to be doing more engaging work, yet their day often gets overrun by addressing urgent IT tickets. But thanks to advances in AI "vibe coding," where a user describes what they want in plain English and the AI turns it into working code, IT teams can automate ticketing workflows and offload much of that work. Password resets that used to take 5 minutes per request now get resolved automatically ...

Governments and social platforms face an escalating challenge: hyperrealistic synthetic media now spreads faster than legacy moderation systems can react. From pandemic-related conspiracies to manipulated election content, disinformation has moved beyond "false text" into the realm of convincing audiovisual deception ...

Traditional monitoring often stops at uptime and server health without any integrated insights. Cross-platform observability covers not just infrastructure telemetry but also client-side behavior, distributed service interactions, and the contextual data that connects them. Emerging technologies like OpenTelemetry, eBPF, and AI-driven anomaly detection have made this vision more achievable, but only if organizations ground their observability strategy in well-defined pillars. Here are the five foundational pillars of cross-platform observability that modern engineering teams should focus on for seamless platform performance ...

For all the attention AI receives in corporate slide decks and strategic roadmaps, many businesses are struggling to translate that ambition into something that holds up at scale. At least, that's the picture that emerged from a recent Forrester study commissioned by Tines ...

From smart factories and autonomous vehicles to real-time analytics and intelligent building systems, the demand for instant, local data processing is exploding. To meet these needs, organizations are leaning into edge computing. The promise? Faster performance, reduced latency and less strain on centralized infrastructure. But there's a catch: Not every network is ready to support edge deployments ...

Every digital customer interaction, every cloud deployment, and every AI model depends on the same foundation: the ability to see, understand, and act on data in real time ... Recent data from Splunk confirms that 74% of the business leaders believe observability is essential to monitoring critical business processes, and 66% feel it's key to understanding user journeys. Because while the unknown is inevitable, observability makes it manageable. Let's explore why ...

Organizations that perform regular audits and assessments of AI system performance and compliance are over three times more likely to achieve high GenAI value than organizations that do not, according to a survey by Gartner ...

Kubernetes has become the backbone of cloud infrastructure, but it's also one of its biggest cost drivers. Recent research shows that 98% of senior IT leaders say Kubernetes now drives cloud spend, yet 91% still can't optimize it effectively. After years of adoption, most organizations have moved past discovery. They know container sprawl, idle resources and reactive scaling inflate costs. What they don't know is how to fix it ...

Artificial intelligence is no longer a future investment. It's already embedded in how we work — whether through copilots in productivity apps, real-time transcription tools in meetings, or machine learning models fueling analytics and personalization. But while enterprise adoption accelerates, there's one critical area many leaders have yet to examine: Can your network actually support AI at the speed your users expect? ...

The more technology businesses invest in, the more potential attack surfaces they have that can be exploited. Without the right continuity plans in place, the disruptions caused by these attacks can bring operations to a standstill and cause irreparable damage to an organization. It's essential to take the time now to ensure your business has the right tools, processes, and recovery initiatives in place to weather any type of IT disaster that comes up. Here are some effective strategies you can follow to achieve this ...