Geographic Maps in Skylar One
ScienceLogic Principal Product Manager Jonathan Chivers introduces the first release of Geographic Maps in Skylar One, a new capability that brings location intelligence to IT operations. Geographic Maps allows users to ingest and align location data with devices, then automatically place them on an interactive map based on known locations. This helps operations teams quickly understand the health and scope of their environments, whether local, regional, or global. Built for NOC teams, analysts, and technology owners, Geographic Maps improves situational awareness and supports faster issue resolution. Jonathan also highlights what’s next on the roadmap, including Business Services mapping, high-fidelity zoomable maps, and location management directly within the Skylar One interface.Introducing the New ScienceLogic AI Platform – ScienceLogic's Next Era in Observability, Automation, and AI
At Nexus Live on October 8 th , we announced an important evolution of the ScienceLogic AI Platform: a new, unified naming convention under the Skylar™ name. This rebrand highlights our commitment to clarity and represents the investments we’ve made to deliver an industry-leading observability platform powered by visionary AI technology. What’s Changing The ScienceLogic AI Platform offerings are now: Skylar One (formerly SL1) Skylar Compliance (formerly Restorepoint) Skylar Automation (formerly PowerFlow) Skylar AI: Analytics (no change) Skylar AI: Advisor (no change) Skylar AI: Automated RCA will be retired as a standalone offering. Its capabilities will be integrated into upcoming Skylar Advisor releases, simplifying our offering for customers and providing broader and more powerful capabilities. Why This Change Matters Over the past 20+ years, ScienceLogic has continuously innovated and expanded through strategic investments and acquisitions. By consolidating our best-in-class offerings under the Skylar name, we: Simplifying our naming, reducing customer and market confusion Reflect tighter interoperability across products Deliver a more seamless, AI-driven experience This platform rebrand is about clarity, scale, and our long-term commitment to accelerating AI-led transformation. What to Expect Next You’ll start seeing Skylar naming convention across our website, content, Nexus Community, customer portal, products, and communications. Supporting resources, including documentation, certifications, training, and knowledge base articles, will be updated over time, aligned with product releases and version retirements, to minimize disruption. Need Help? For more details, please visit the Press Release and Skylar Renaming Page or reach out to your account team We’re excited to bring you along on this next chapter in our journey. The ScienceLogic Team View a special message from Dave Link and Douglas James.Using Skylar RCA for Root Cause Analysis
This article assumes you already have a Skylar RCA account. If not, please contact your CSM for a 30-day trial of the product. Step 1: Contact ScienceLogic support to obtain a copy of the OTel collector. Step 2: Install the OTel collector as per installation steps (see the references section below) Step 3: Update the OTel configuration file. This is the otelcol.yaml file in otelcol-sciencelogic-zebrium_x86_64 directory. The following fields will need to be updated Include attribute in filelog block to match the log file location(s) regex in operators > type block. This needs to match the log file format. As a best practice, use a regular expression checker (for example, https://regex101.com/ , to check your regular expression before updating the configuration file endpoint and ze_token sections in the exporters block. These need to be copied from your Skylar RCA instance Step 4: Before sending logs to Skylar, it is recommended configuration is tested with local debugging. This can be achieved by using exporters: [debug] in the service: pipelines: logs: section of the otelcol.yaml config file. Also, in the receivers: filelog: section, add the line start_at: beginning to force the collector to read logs from the beginning. This will generate a log file in the logs sub-directory. Step 5: Restart the SciencelogicZebriumOpenTelemetryCollector service. Step 6: Once you are happy with the debug output, modify the config file so that logs will be sent to Skylar RCA. Remember to Restart the SciencelogicZebriumOpenTelemetryCollector service. Step 7: After a few minutes, check the Ingest History on the Skylar UI (in Ingest-history) to verify data is being received. Also, Diagnostics menu can provide useful information about how many log lines were received in the last 4 hours. Go to the Diagnostics menu and click on ‘Run Now’ button. References: Skylar Automated RCA documentation: https://docs.sciencelogic.com/latest/Content/Web_Zebrium/home_RCA.htm Windows OTel collector: https://docs.sciencelogic.com/latest/Content/Web_Zebrium/03_Log_Collectors_Uploads/Windows_OTel.html
