v.208 Edwin AI

We are excited to announce that we have rebranded Dexda to Edwin AI.

We chose the name Edwin AI, after Edwin Hubble, the American astronomer who is the namesake of the Hubble telescope. He discovered the two moons of Pluto (Nix and Hydra) and helped determine the rate at which the universe is expanding. Since its mission began in 1990, the Hubble telescope has made more than 1.6 million observations.

Just as Edwin Hubble invented modern-day cosmology and transformed our understanding and limited view of the universe, we think Edwin AI will pave the way for modern enterprise observability and transform how customers perceive, reason, and act on their complex observability data.

For more information, see Introduction to Edwin AI in the product documentation.

We have added a related links section to config records to enable easier navigation to screens related to that record. To view this, go to Configuration, and select a record. You can view the links associated with this config record, such as the Import Set Rows or the Business Rule, without having to navigate to the specific tab.

For more information, see Configuration Records.

You can now view the decrypted value of API keys for specific endpoints in domain-separated installs. To do so, go to Domain separation > Endpoints > Decrypt API Key.

For more information, see Enabling Domain Support product documentation.

You can import all outbound field maps from outbound transform maps associated with CMDB parent classes. To import, navigate to LogicMonitor Data Exchange > Configuration > Outbound transform map. Select a record and select Import parent class field maps.

For more information, see Outbound Transform Maps and Field Maps.

You can now make specific Config records read-only using the Disable inbound option. To do so, go to LogicMonitor Data Exchange > Configuration. Select a record and then select the corresponding Disable inbound checkbox.

Note: This option does not affect CMDB-related configs, which are always read-only.

For more information, see Completing default configuration.

LogicMonitor has introduced the following feature for inbound payloads:

Target record information

Now, when an inbound payload record is processed, it is possible to see the target record, target table, and action that occurred.
To access this feature, navigate to LogicMonitor Data Exchange > Payloads > Inbound payload.
Action shows the action that occurred (For example, inserted or updated). Target table what table it is written to. The target record is a direct link to the record that the inbound payload affected.

Strict Mode

You can now make LMDX behave more strictly, causing any warning (For example, being unable to set a value due to a missing field on the import set table) to be an error.
To access this feature, navigate to LMDX properties > LMDX config record properties > Inbound payload processing strict mode.