Node Navigation
Recent Content
Azure monitoring and integration with CMDB
When gathering information from cloud stuff, or actually doing whatever with cloud staff you most often need the object's ID, that long hexastring. That same ID is also most used identifier and required information when trying to sync those cloud "devices" into ServiceNow CMDB. The issue is that SL1 Azure PP does not gather that information too much, one device class that we have so far found it is those actual VMs in cloud. But one could say that those are the only "devices" where it is easily found. So my question is, how you have planned, or done, the CMDB integration of Azure cloud stuff. Or have you done any automation from SL1 to Azure, because also there one always(?) need that object ID. I could have written also an Idea for this, but at least for me, Nexus does not support my ideas.4Views0likes0CommentsWeek of April 22, 2024
1 MIN READ Since the last update there are no new articles to share. Stay tuned for future updates.jtriplett20 hours agoPlace Latest KB Articles and Known Issues BlogLatest KB Articles and Known Issues BlogModerator5Views1like0CommentsDevice configuration "key/value" pairs synchronization to ITSM
With Powerflow most data are pretty easy to sync from SL1 to ITSM/CMDB, in this case ServiceNow. But now we have requirement that we should sync cloud device tags from SL1 to SN. The data from Azure virtual server, using Azure PP, is shown on SL1 like below, multiple key/value rows per device. So those are not easily stored into Attributes. And if I have understood correctly, quite a lot of tags used in cloud. Any ideas how these could be synced with PF into ServiceNow?63Views1like4CommentsNexus Community Weekly Highlights- #1
Hello Nexus Community Members, Here we are in Week 4after our bigcommunity launch. We will be sharing weekly highlights from the community including topics: Featured content Welcome to new members Programs & Upcoming Events Call-out for ideas Be sure to review these helpful resources: Nexus- ScienceLogic Community Member Guidelines Nexus Community Tip: Community Do’s and Don’ts Nexus Community Tip: Follow Areas & Content for updates Today we want to welcome new Nexus Community Members who are early-adopters and joined in March justinelborough jpresley Colin jamesramsden jbovee bailey PattyN Thank you for joining the community we look forward to working with you. Feel free to share your ideas and feedback so we can get you the most helpful resources and information. Cheers, Sara Leslie- Community Manager32Views2likes0CommentsNexus Community Tip: Community Do’s and Dont’s
Guidance on behaviors that help benefit members and the community. Our goal is to help you get answers, learn and collaborate with others. We find that this outline offers assistance to new membes. Do’s Be professional and respectful; it helps build trust. Answer questions to the best of your ability. Ask for more information if needed to give an honest answer. Share your knowledge but be succinct and to the point. Welcome new members! You can tell who they are by their community rank. Be kind, inclusive and patient. Please remember that members have differing levels of experience and may not be native English language speakers. Practice humility: arrogance slows progress. Always try your best to stay on topic. Have fun and be authentic! Create your own brand. Report spam or inappropriate content. Always abide by the Community Guidelines. Participate in healthy brainstorming conversations, just be respectful even when you disagree. If in doubt- contact the community manager sara.leslie@sciencelogic.com Don’ts Be disrespectful or rude to any member at any time. Post or attach any information that shares private information, about yourself, others, or a company. Post content that infringes on intellectual property, privacy or other rights of yours, your employers or third parties. Post negative content regarding ScienceLogic, other community members, other companies, or our partners. Be hesitant to share your questions or ideas- all participation is valuable.48Views2likes0CommentsNexus Community Tip: Follow Areas & Content for updates
An important part of joining the Nexus Community is to locate the areas and content you are the most interested in and create alerts, so you are aware of updates. You can follow content in several different ways. You can follow content at the Category Level: Discussion Forums, Blogs, Resource Library etc. Page Level: Specific Discussion Forum, Blog or Resource Type etc. Content Level: Individual Discussion, Blog post or Resource etc. Here’s How Login Click on the ‘Bell Icon’ on the right-hand corner Select the area or content you want to subscribe to for updates You can also unsubscribe the same way10Views0likes0CommentsWeek of April 15, 2024
1 MIN READ On a weekly basis ScienceLogic Technical Support will post PowerPacks and SyncPacks which released the previous or current week.renecantwell8 days agoPlace PowerPack Release Notifications BlogPowerPack Release Notifications BlogModerator14Views0likes0CommentsWeek of April 15, 2024
1 MIN READ A set of Knowledgebase Articles published last week is listed below. All KBAs can be searched via Global Search on the Support Portal and filtered by various components like product release.renecantwell8 days agoPlace Latest KB Articles and Known Issues BlogLatest KB Articles and Known Issues BlogModerator9Views0likes0CommentsBuilding Effective Run Book Automations: Maximizing Operational Efficiency with SL1
2 MIN READ In today's dynamic IT landscape, operational efficiency and control are paramount for businesses to stay competitive and resilient. ScienceLogic'sRun Book Automation (RBA) offers a comprehensive solution aimed at streamlining operations, enhancing control, and identifying critical events. In SL1, creating an automation policy will define the event conditions that must be met before SL1 will trigger an automatic action. Consider a scenario where an unplanned network device configuration change triggers a compliance alert in SL1, but the alert doesn’t provide all the information necessary to determine the best action for resolution. ScienceLogic’s automations can collect additional event information through a python script and return the data to SL1 and/or your incident platform. With this full information set, the best course for remediation can be determined. If appropriate, automations can also assist with resolution steps to avoid human error as you work to reduce your mean time to repair (MTTR). This systematic approach ensures that key events are promptly addressed, reducing the risk of compliance violations and operational disruptions. Operational efficiency is further enhanced through tailored automation actions that alleviate repetitive tasks. Another common scenario is for a web server supporting the front-end of your most important application to have a performance problem that can come and go at a moment's notice. At the time of occurrence, the SL1 platform can trigger an automation to collect the necessary data that allows your support team to decide on the best resolution. Furthermore, if the resolution also includes a scriptable solution (and SL1 has many) the resolution step can be performed and tracked, therefore reducing MTTR. ScienceLogic RBAs offer a powerful solution by identifying critical events, streamlining processes, and enhancing operational control. With the ability to align automation policies with critical events, organizations can adapt to evolving challenges with agility and confidence. To learn about how to build effective RBAs to maximize your operational efficiency with SL1, attend our upcoming PowerHour session on April 24, 2024. I’ll walk you through how to align automation policies with critical events and how to create automations that help reduce repetitive tasks. If you have automation questions leading up to the event, let me know. Post them below!24Views2likes0CommentsRestorepoint User Group
Restorepoint Product Management would like to invite customers who are actively using Restorepoint to Nexus ScienceLogic Community | Group: Restorepoint User Group. What you will get out of the user group: Get demos of unreleased features & give feedback Exchange ideas Share tips and learn best practices Help Product Management prioritize Participate in beta versions Time commitment: 1 hour every other month10Views1like0CommentsEnd-of-Life of Restorepoint Older Versions
We would like to bring to your attention the following End of Life (EOL) updates that may impact the Restorepoint version or operating system you are currently using: EOL Restorepoint v5.4: May 30, 2024 EOL Restorepoint v5.5: August 31, 2024 EOL of all Restorepoint versions that running on any version of CentOS: August 31, 2024 Please note any support issues arising from these product versions will not be addressed after the specified EOL dates. The only exception will be for customers who have bought Restorepoint hardware that came with CentOS. We will support these customers until their hardware reaches end-of-life. Our latest Restorepoint version is v5.6, and all enhancements and bug fixes after August 31, 2024, will be exclusively available for this version. To facilitate your migration from CentOS to Oracle Linux 8, we have prepared a comprehensive migration guide. We encourage you to consult this guide both before and during the migration process. Should you have any further inquiries or need assistance, please contact our support team. Read Migration Guide20Views1like0Comments