The APMdigest Vendor Forum was established to give vendors of Application Performance Management (APM), NPM, EUEM, ITOA and related technologies an opportunity to share their views with the IT community in an objective venue. All commentary in Vendor Forum blogs is intended to be objective, vendor-neutral and non-promotional content to educate and enlighten APMdigest readers.
All vendors in APM, NPM, EUEM, ITOA and related market spaces are welcome to blog on the Vendor Forum at no cost. To request a blogging account on the Vendor Forum, contact Pete Goldin, Editor and Publisher of APMdigest.
The following guidelines apply to software vendors who would like to post a blog on APMdigest. Non-vendor blogs are posted in The BSM Blog. If you work for or represent a company or organization that is not considered a product vendor by APMdigest, and you want to submit a blog, click here for the Editorial 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.
Signing Up for a Vendor Forum Blogging Account
■ A request for a blogging account on the Vendor Forum must come directly from the individual whose name will be on the blogs, from that individual's corporate email address.
■ Only one representative from each vendor will be allowed to maintain a blogging account on the Vendor Forum at any particular time, if that vendor does not sponsor APMdigest. Once a company's blogger is established, that same byline must be used for all future blogs from that company. The only time the byline can be changed is if the blogger is no longer with the company; the blogger has moved to a different part of the company and no longer has any involvement with APM or related technologies; or the blogger is no longer blogging and has not posted a blog in the last 24 months.
■ APMdigest sponsors are allowed multiple blogging accounts on the Vendor Forum. This sponsor benefit is especially helpful for companies with multiple thought leaders in the industry who would like to claim authorship for their own blogs. With an APMdigest sponsorship, your CEO, CTO, CMO, technology evangelists and others can all blog. Click here to find out how you can sponsor APMdigest. Click here for the Sponsor Blog Guidelines.
■ Blogs go with the blogger. This means if a blogger leaves a company, moves to a new company in the APM industry or a related market, and continues to blog, all blogs posted by that blogger – past and present – will reference the new company. References to the previous company will be removed from the previous blogs. Exceptions to this rule can be made for sponsors, if requested.
Rules for Blogging on the Vendor Forum
Please observe the following rules when blogging on the Vendor Forum:
■ 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. (In the past, bloggers could login and post their own blogs but this practice has been discontinued due to formatting issues.)
■ APMdigest does not accept any blog submissions from gmail or other anonymous email accounts. You must send the blog from your corporate email account.
■ Do not promote your own company, products, services, resources, events or partners in blogs on the Vendor Forum. Topics should be general industry interest. Copy and graphics should be non-promotional and vendor-neutral.
■ One reference to your company in the blog copy is permitted when you are discussing a survey or report conducted or commissioned by your company. A reference to your company's or partner's product is never permitted in the blog copy.
■ 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.
■ Do not use your product names or phrases that refer to your specific product or service in a blog. Even if your company is trying to turn the phrase into an industry term, if only your company uses this term and it basically refers to your product or service, do not include the phrase in a blog.
■ Case studies are not permitted on the Vendor Forum. Do not reference your customer in a blog, or talk about or imply how your company or products helped a customer.
■ 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, when the blog is about solving performance issues relating to a specific environment or infrastructure brand, exceptions to this rule can be made on a case-by-case basis.
■ Do not reference open source brand names in a blog if the technology is related to APM, ITOA, NPM, or any of the technologies covered by APMdigest. A reference to other open source projects is sometimes permitted, as long as the reference is to the open source project or technology itself, and not the company that founded or owns the project.
■ Companies that do not sponsor APMdigest can only include a link to their company home page at the end of the blog – no product pages or any other pages. Even if the product has its own URL separate from the company page, this cannot be included in place of the company home page. The home page link will always be included in the "Related Links" section at the end of the blog, and cannot be substituted with a hyperlink in the text. The home page link cannot include any tracking code.
■ Only sponsors of APMdigest can include additional links at the end of the blog. Click here to find out how you can sponsor APMdigest.
■ APMdigest removes old outdated links, but only updates outdated links for current sponsors of the site.
■ Do not place any hyperlinks in the body copy of a blog linking to your company's or any other vendor's web pages or other promotional pages. Hyperlinks in the body copy should only be to support factual points you are making. These hyperlinks can link to a supporting report or article as long as the content is not on your website or any other vendor's website, is not sponsored or commissioned by your company or any other vendor, and does not promote your company or any other vendor in any way. Hyperlinks cannot include any tracking code. Inclusion of any hyperlinks is at the sole discretion of APMdigest.
■ When supporting a fact in your blog with a hyperlink, only link to content that is not gated. For example, do not link to gated analyst reports that require the reader to purchase the report or a subscription in order to access the report.
■ Try to keep blogs between 500-1000 words. This is more of a guideline than a rule. You can include more content if you wish, but APMdigest recommends posting shorter blogs more often. If you have written a 1000+ word blog, consider breaking it into two or more blogs. You could call them Part One and Part Two, if you like. If a blog is lengthy, APMdigest may choose to post it in multiple parts.
■ 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. Vendor Forum blog posts are edited by APMdigest for spelling, basic grammar and punctuation. Vendor Forum blogs are also edited to ensure they meet APMdigest guidelines.
■ 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.
■ The date the blog is actually published will be decided by the editor. APMdigest may provide you with an estimated publication date prior to posting, but that date cannot be guaranteed, as unforeseen priorities may push the posting date back. APMdigest sponsors have priority when blogs are posted.
■ All Vendor Forum blogs must be original content that has not been published – and will not be published – on any other website. 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 will always send an email to the main contact(s) when a blog posts, with the URL. If you have not rec'd an email, your blog has not posted yet.
■ You can re-post your blogs from the Vendor Forum on your own blogs or websites, as long as you mention that the blog was originally posted on APMdigest, and include a link to APMdigest. 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.
■ Please note that these guidelines are updated periodically to ensure continued alignment with APMdigest's mission.
Topics for the Vendor Forum
If you are unsure whether your topic fits APMdigest, run your idea by Pete Goldin.
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.
Modern complex systems are easy to develop and deploy but extremely difficult to observe. Their IT Ops data gets very messy. If you have ever worked with modern Ops teams, you will know this. There are multiple issues with data, from collection to processing to storage to getting proper insights at the right time. I will try to group and simplify them as much as possible and suggest possible solutions to do it right ...
In Agile, development and testing work in tandem, with testing being performed at each stage of the software delivery lifecycle, also known as the SDLC. This combination of development and testing is known as "shifting left." Shift left is a software development testing practice intended to resolve any errors or performance bottlenecks as early in the software development lifecycle (SDLC) as possible ...
Overwhelmingly, business leaders cited digital preparedness as key to their ability to adapt, according to an in-depth study by the Economist Intelligence Unit (EIU), looking into how the relationship between technology, business and people evolved during the COVID-19 pandemic ...
Robotic Data Automation (RDA) is a new paradigm to help automate data integration and data preparation activities involved in dealing with machine data for Analytics and AI/Machine Learning applications. RDA is not just a framework, but also includes a set of technologies and product capabilities that help implement the data automation ...
There is no one-size-fits-all approach to changing the experience of employees during a pandemic, but technological innovation can have a positive impact on how employees work from home as companies design their digital workspace strategy. The IT team supporting this shift needs to think about the following questions ...
Downtime. It's more than just a bar on the Rebel Alliance's base on Folor. For IT Ops teams, downtime is not fun. It costs time, money and often, user frustration. It takes more than the Force to handle incidents ... it takes an intergalactic team. An effective incident management team is made up of people with many different skill sets, styles and approaches. We thought it would be fun to map the heroes of IT Ops with Star Wars characters (across Star Wars generations) based on their traits ...
Vendors and their visions often run ahead of the real-world pack — at least, the good ones do, because progress begins with vision. The downside of this rush to tomorrow is that IT practitioners can be left to ponder the practicality of technologies and wonder if their organization is ahead of the market curve or sliding behind in an invisible race that is always competitive ...
According to a new report, Digital Workspace Deployment & Performance Monitoring in the New Normal, 82% of respondents had changes in their digital workspaces due to the pandemic ...
There are a few best practices that DevOps teams should keep in mind to ensure they are not lost in the weeds when incorporating visibility and troubleshooting programs into their systems, containers, and infrastructures. Let's dive into these best practices ...