{"id":2365,"date":"2026-08-13T09:00:00","date_gmt":"2026-08-13T01:00:00","guid":{"rendered":"https:\/\/cnbygele.com\/blog\/event-triggered-harmonic-logging-intermittent-loads\/"},"modified":"2026-08-13T09:00:00","modified_gmt":"2026-08-13T01:00:00","slug":"event-triggered-harmonic-logging-intermittent-loads","status":"publish","type":"post","link":"https:\/\/cnbygele.com\/ru\/blog\/event-triggered-harmonic-logging-intermittent-loads\/","title":{"rendered":"\u0424\u0438\u043a\u0441\u0430\u0446\u0438\u044f \u043f\u0435\u0440\u0435\u043c\u0435\u0436\u0430\u044e\u0449\u0438\u0445\u0441\u044f \u0433\u0430\u0440\u043c\u043e\u043d\u0438\u0447\u0435\u0441\u043a\u0438\u0445 \u044f\u0432\u043b\u0435\u043d\u0438\u0439 \u0441 \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u044c\u044e \u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0438 \u0437\u0430\u043f\u0438\u0441\u0435\u0439"},"content":{"rendered":"<div class=\"b2b-article\">\n<p style=\"margin:0 0 16px;line-height:1.7\">Intermittent-load investigations often need more than a long average trend. Event-triggered harmonic logging can preserve what happened at a named electrical boundary when a defined condition occurred, provided that the trigger settings, clock, meter setup, and operating state are saved with the record.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">For broader planning context, start with the <a href=\"https:\/\/cnbygele.com\/ru\/power-quality-system-guides\/\">\u0440\u0443\u043a\u043e\u0432\u043e\u0434\u0441\u0442\u0432\u0430 \u043f\u043e \u0441\u0438\u0441\u0442\u0435\u043c\u0430\u043c \u043a\u0430\u0447\u0435\u0441\u0442\u0432\u0430 \u044d\u043b\u0435\u043a\u0442\u0440\u043e\u044d\u043d\u0435\u0440\u0433\u0438\u0438<\/a>. This article explains how to organize event evidence; it does not identify a root cause, prescribe a device, or promise an operating result.<\/p>\n<figure style=\"margin:26px 0;text-align:center\"><img decoding=\"async\" style=\"max-width:640px;width:100%;height:auto;display:block;margin:0 auto;border-radius:8px\" src=\"https:\/\/cnbygele.com\/wp-content\/uploads\/2026\/04\/21.JKWS_.webp\" alt=\"CNBYG controller for documenting an event-triggered harmonic logging plan\" \/><\/figure>\n<nav class=\"b2b-toc\" style=\"background:#f5f8fa;padding:16px 20px;border-radius:8px;margin:0 0 24px\">\n<h2 id=\"contents\" style=\"margin:42px 0 14px;scroll-margin-top:96px\">\u0421\u043e\u0434\u0435\u0440\u0436\u0430\u043d\u0438\u0435<\/h2>\n<ul style=\"margin:0 0 18px 1.2em;line-height:1.7\">\n<li style=\"margin:0 0 8px\"><a href=\"#part-1-define-the-event-question-before-enabling-triggers\">Part 1. Define the event question before enabling triggers<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"#part-2-choose-a-trigger-that-can-be-reviewed-later\">Part 2. Choose a trigger that can be reviewed later<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"#part-3-keep-electrical-and-operating-clocks-together\">Part 3. Keep electrical and operating clocks together<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"#part-4-compare-repeatable-events-at-the-same-boundary\">Part 4. Compare repeatable events at the same boundary<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"#part-5-separate-event-evidence-from-a-mitigation-promise\">Part 5. Separate event evidence from a mitigation promise<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"#part-6-send-an-event-record-package-with-the-rfq\">Part 6. Send an event record package with the RFQ<\/a><\/li>\n<\/ul>\n<\/nav>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"direct-answer\">\u041f\u0440\u044f\u043c\u043e\u0439 \u043e\u0442\u0432\u0435\u0442<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">Set a reviewable trigger, retain the electrical boundary and capture settings, and log the operating condition at the same time. Then compare events collected under like conditions before treating them as evidence for a project discussion.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-1-define-the-event-question-before-enabling-triggers\">Part 1. Define the event question before enabling triggers<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">Write the question before choosing a trigger. A team may want to capture a recurring process transition, a repeated start sequence, a switching change, or an unexplained alarm window. Each requires a named electrical location and a clear description of the event the record is expected to catch.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">Mark the meter, CT, voltage reference, and included circuits on the one-line diagram. Keep the project question beside the location. This prevents a local capture from being described later as a complete plant record.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\"><strong>\u0412\u0430\u0436\u043d\u043e:<\/strong> Do not treat an event waveform as proof of a root cause or a mitigation result. The electrical boundary, operating condition, and project acceptance method need separate definition (<a href=\"https:\/\/standards.ieee.org\/ieee\/519\/5892\/\" rel=\"nofollow noopener\" target=\"_blank\">\u041e\u0431\u0437\u043e\u0440 IEEE 519<\/a>).<\/p>\n<table style=\"width:100%;border-collapse:collapse\">\n<thead>\n<tr>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Event question<\/th>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Boundary to document<\/th>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">\u0414\u043e\u043a\u0430\u0437\u0430\u0442\u0435\u043b\u044c\u0441\u0442\u0432\u0430 \u0434\u043b\u044f \u0441\u043e\u0445\u0440\u0430\u043d\u0435\u043d\u0438\u044f<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Repeatable process transition<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Defined process feeder<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Process state, trigger time, and included load groups<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Switching-related observation<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Selected bus or feeder<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Switching state, meter setup, and prior\/post window<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Alarm or trip review<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Agreed electrical location<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Alarm clock, event export, and operating log<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-2-choose-a-trigger-that-can-be-reviewed-later\">Part 2. Choose a trigger that can be reviewed later<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">Choose a trigger that another reviewer can understand from the report. Record the trigger type, threshold or event rule as configured, pre-event and post-event duration, sampling or aggregation setting, and any holdoff logic. The aim is not to collect the largest number of files; it is to collect records that can be compared.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">Avoid using a vague description such as &#8220;high harmonics&#8221; as the only trigger note. Include the original instrument export and a short configuration note. If settings change during the collection period, label the events as separate series.<\/p>\n<table style=\"width:100%;border-collapse:collapse\">\n<thead>\n<tr>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Trigger-record item<\/th>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Keep with the export<\/th>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">\u041e\u0431\u0437\u043e\u0440 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u044f<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Trigger rule<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Instrument field or documented event condition<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Shows why the capture started.<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Time window<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Pre-event, event, and post-event period<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Supports comparison across similar events.<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Meter setup<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">CT ratio, voltage reference, and configuration<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Identifies what the record includes.<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Configuration change<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Date and reason for changed settings<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Stops unlike captures being merged.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-3-keep-electrical-and-operating-clocks-together\">Part 3. Keep electrical and operating clocks together<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">An event record needs both an electrical clock and an operating log. Note the shift, process state, active drive groups, rectifiers, UPS loads, starts, stops, transfers, capacitor switching, bypass condition, and source arrangement. A timestamp alone does not show what the plant was doing.<\/p>\n<figure style=\"margin:26px 0;text-align:center\"><img decoding=\"async\" style=\"max-width:640px;width:100%;height:auto;display:block;margin:0 auto;border-radius:8px\" src=\"https:\/\/cnbygele.com\/wp-content\/uploads\/2026\/04\/22.JKWS_.webp\" alt=\"CNBYG controller terminal view for documenting event capture connections\" \/><\/figure>\n<p style=\"margin:0 0 16px;line-height:1.7\">Synchronize clocks where the available tools allow it, then state any known uncertainty in the report. The objective is traceability, not a claim that every event has the same cause. The <a href=\"https:\/\/cnbygele.com\/ru\/blog\/voltage-flicker-welding-loads-pst-measurement\/\">event and flicker measurement context<\/a> article is a separate example of why operating state belongs beside power-quality data.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-4-compare-repeatable-events-at-the-same-boundary\">Part 4. Compare repeatable events at the same boundary<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">Compare event captures only when the electrical location and measurement configuration are known. Group records by similar process condition, then check whether the trigger, load state, and waveform or current evidence are consistent. A single anomalous capture may be important, but it should be labeled as an isolated observation until similar evidence is available.<\/p>\n<table style=\"width:100%;border-collapse:collapse\">\n<thead>\n<tr>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Comparison question<\/th>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Keep constant or disclose<\/th>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">Avoid assuming<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Was the same boundary used?<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Meter, CT, and voltage reference<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">That two feeders describe the same load mix.<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Was the operating state similar?<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Process condition and major loads<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">That every shift is equivalent.<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Did the trigger rule change?<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Configuration and time window<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">That all captures were started the same way.<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Was another event coincident?<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Switching, source, or maintenance note<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">That harmonic current explains every observation.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p style=\"margin:0 0 16px;line-height:1.7\">For a broader collection checklist, see <a href=\"https:\/\/cnbygele.com\/ru\/blog\/power-quality-metering-before-apf-svg-rfq\/\">\u0438\u0437\u043c\u0435\u0440\u0435\u043d\u0438\u0435 \u043f\u043e\u043a\u0430\u0437\u0430\u0442\u0435\u043b\u0435\u0439 \u043a\u0430\u0447\u0435\u0441\u0442\u0432\u0430 \u044d\u043b\u0435\u043a\u0442\u0440\u043e\u044d\u043d\u0435\u0440\u0433\u0438\u0438 \u043f\u0435\u0440\u0435\u0434 \u0437\u0430\u043f\u0440\u043e\u0441\u043e\u043c \u043f\u0440\u0435\u0434\u043b\u043e\u0436\u0435\u043d\u0438\u0439<\/a>. It organizes evidence but does not certify a plant condition.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-5-separate-event-evidence-from-a-mitigation-promise\">Part 5. Separate event evidence from a mitigation promise<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">Event data can help define a review scope, but it does not select equipment by itself. Before an AHF\/APF discussion, establish the harmonic-current objective, connection point, CT arrangement, representative load record, protection coordination, installation constraints, cable route, cooling, communications, and acceptance method.<\/p>\n<p style=\"margin:0 0 16px;line-height:1.7\">\u0417\u0435\u043c\u043b\u044f <a href=\"https:\/\/cnbygele.com\/ru\/product\/ahf-active-harmonic-filter-harmonic-control\/\">\u041a\u043e\u043d\u0442\u0435\u043a\u0441\u0442 \u043f\u0440\u043e\u0434\u0443\u043a\u0442\u0430: \u0410\u043a\u0442\u0438\u0432\u043d\u044b\u0439 \u0433\u0430\u0440\u043c\u043e\u043d\u0438\u0447\u0435\u0441\u043a\u0438\u0439 \u0444\u0438\u043b\u044c\u0442\u0440 AHF<\/a> page is a starting point for a defined harmonic-current question. It does not guarantee removal of an event, prevention of a trip, or a particular operating result.<\/p>\n<figure style=\"margin:26px 0;text-align:center\"><img decoding=\"async\" style=\"max-width:640px;width:100%;height:auto;display:block;margin:0 auto;border-radius:8px\" src=\"https:\/\/cnbygele.com\/wp-content\/uploads\/2026\/04\/23.JKG2B.webp\" alt=\"CNBYG controller shown as product context after an event record review\" \/><\/figure>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"part-6-send-an-event-record-package-with-the-rfq\">Part 6. Send an event record package with the RFQ<\/h2>\n<p style=\"margin:0 0 16px;line-height:1.7\">Package the event evidence so a reviewer can trace it back to the plant condition. Include both original exports and the notes needed to interpret them.<\/p>\n<table style=\"width:100%;border-collapse:collapse\">\n<thead>\n<tr>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">\u041f\u043e\u043a\u0443\u043f\u0430\u0442\u0435\u043b\u044c \u0434\u043e\u043b\u0436\u0435\u043d \u043f\u0440\u0435\u0434\u043e\u0441\u0442\u0430\u0432\u0438\u0442\u044c<\/th>\n<th style=\"border:1px solid #d9e1e8;padding:9px 12px;background:#f5f8fa;text-align:left\">\u041f\u043e\u0447\u0435\u043c\u0443 \u044d\u0442\u043e \u0432\u0430\u0436\u043d\u043e<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">One-line diagram and declared nominal system information<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Defines the electrical boundary and supply context.<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Meter, CT, and voltage-reference positions<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Identifies the actual measurement location.<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Trigger rule, settings, and event exports<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Makes the capture method reviewable.<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Clock reference and operating-state log<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Connects events to plant operation.<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Load inventory and existing equipment<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Identifies the context around each capture.<\/td>\n<\/tr>\n<tr>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Protection, installation limits, and acceptance requirements<\/td>\n<td style=\"border:1px solid #d9e1e8;padding:9px 12px\">Defines integration and project boundaries.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p style=\"margin:0 0 16px;line-height:1.7\">CNBYG can discuss product-line fit after the event records establish a defined harmonic-current objective. Use <a href=\"https:\/\/cnbygele.com\/ru\/contact-us\/\">the event record package<\/a> to begin that conversation; this guide cannot replace a root-cause study or promise a project result.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"frequently-asked-questions\">\u0427\u0430\u0441\u0442\u043e \u0437\u0430\u0434\u0430\u0432\u0430\u0435\u043c\u044b\u0435 \u0432\u043e\u043f\u0440\u043e\u0441\u044b<\/h2>\n<h3 style=\"margin:28px 0 12px\">What is event-triggered harmonic logging?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">It is a method of capturing electrical records when a documented event condition occurs. The record should include the trigger rule, electrical location, time window, meter setup, and operating state.<\/p>\n<h3 style=\"margin:28px 0 12px\">What should trigger a capture?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">Choose a trigger that matches the review question and can be documented later. Save the original instrument setting, the capture window, and any configuration change.<\/p>\n<h3 style=\"margin:28px 0 12px\">Does one event prove a root cause?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">No. One capture can identify an observation, but comparable records, operating context, and project review are needed before assigning cause or selecting mitigation.<\/p>\n<h3 style=\"margin:28px 0 12px\">Why record operating state with an event?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">The active process, load groups, starts, switching, and source arrangement can change what the electrical record represents. The operating log makes comparisons meaningful.<\/p>\n<h3 style=\"margin:28px 0 12px\">Can event data select an APF?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">No. An AHF\/APF review still needs a defined harmonic-current objective, connection point, representative load data, integration constraints, and acceptance scope.<\/p>\n<h3 style=\"margin:28px 0 12px\">What belongs in an event-based RFQ package?<\/h3>\n<p style=\"margin:0 0 16px;line-height:1.7\">Send the one-line diagram, measurement setup, trigger settings, event exports, time and operating logs, load inventory, existing equipment details, and installation constraints.<\/p>\n<h2 style=\"margin:42px 0 14px;scroll-margin-top:96px\" id=\"references\">\u0421\u0441\u044b\u043b\u043a\u0438<\/h2>\n<ul style=\"margin:0 0 18px 1.2em;line-height:1.7\">\n<li style=\"margin:0 0 8px\"><a href=\"https:\/\/standards.ieee.org\/ieee\/519\/5892\/\" rel=\"nofollow noopener\" target=\"_blank\">IEEE 519 resource for harmonic-control context<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"https:\/\/www.nema.org\/standards\/view\/motors-and-generators\" rel=\"nofollow noopener\" target=\"_blank\">NEMA MG 1 reference for motor-system context<\/a><\/li>\n<li style=\"margin:0 0 8px\"><a href=\"https:\/\/www.energy.gov\/cmei\/ito\/industrial-technologies-office\" rel=\"nofollow noopener\" target=\"_blank\">DOE Industrial Technologies Office resources<\/a><\/li>\n<\/ul>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Intermittent-load investigations often need more than a long average trend. Event-triggered harmonic logging can preserve what happened at a named electrical boundary when a defined condition occurred, provided that the trigger settings, clock, meter setup, and operating state are saved with the record. For broader planning context, start with the power quality system guides. This [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":1632,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_gspb_post_css":"","footnotes":""},"categories":[1],"tags":[],"class_list":["post-2365","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog"],"blocksy_meta":{"styles_descriptor":{"styles":{"desktop":"","tablet":"","mobile":""},"google_fonts":[],"version":7}},"acf":[],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/cnbygele.com\/ru\/wp-json\/wp\/v2\/posts\/2365","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cnbygele.com\/ru\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cnbygele.com\/ru\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cnbygele.com\/ru\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/cnbygele.com\/ru\/wp-json\/wp\/v2\/comments?post=2365"}],"version-history":[{"count":0,"href":"https:\/\/cnbygele.com\/ru\/wp-json\/wp\/v2\/posts\/2365\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cnbygele.com\/ru\/wp-json\/wp\/v2\/media\/1632"}],"wp:attachment":[{"href":"https:\/\/cnbygele.com\/ru\/wp-json\/wp\/v2\/media?parent=2365"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cnbygele.com\/ru\/wp-json\/wp\/v2\/categories?post=2365"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cnbygele.com\/ru\/wp-json\/wp\/v2\/tags?post=2365"}],"curies":[{"name":"\u0432\u043f","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}