Group Content
Featured Content
Boards
Product Documentation
14 days ago59 Posts Product Documentation
9 months ago1 Post Product Documentation
0 Posts Product Documentation
0 Posts
Recent Content
Share your Product Documentation questions, issues, and ideas here.
The ScienceLogic Documentation would like to hear from you! This discussion area is where you can let us know if you have any suggestions for the various docs sites at https://docs.sciencelogic.com/. This includes: Areas where the documentation might be missing key information. Suggestions for examples in the docs. Out-of-date or deprecated content. Typos! Errors in the docs. Areas where the docs are confusing or hard to navigate. Issues with the search. Bad links. Or anything else about the docs you'd like to share. TIP: You can Reply to this page, or simply click the dark blue Start a Discussion button at top right to share your info about the docs with the doc team. Thanks so much!Solved241Views3likes12CommentsNo documentation on how to logon/logoff when using gql directly
The documentation about the ScienceLogic GraphQL API only mentions a login procedure when using the /gql endpoint. There is no information about how to log on (or log off) on the ScienceLogic platform and then use the API. Link to the documentation: https://docs.sciencelogic.com/latest/Content/Web_Content_Dev_and_Integration/GraphQL_API/graphql_introduction.htm#authentication-and-user-access For Logon, I have found a way to achieve this: execute a GET request to <platformURI>/authenticate with basic authentication, using a valid SL1 Local user information. From the response received, save the cookie information for later Any subsequent call to the /gql endpoint (inserting the cookie information on each request) allows me to execute gql queries/mutations. I can also reuse that same cookie information if I want to execute REST API actions. However, I do not succeed in 'forcing' a logoff from my previously created session: whatever I do, my session remains active and usable in the System > Monitor > Audit Logs. Only when I explicitly kill the session in that screen is my session invalid and I must login again. Can this be added to the documentation please?135Views2likes5CommentsThis week's updates to the Doc sites at docs.sciencelogic.com
8/1/25 Doc updates to the main docs site at https://docs.sciencelogic.com/: Updated the manual for the Skylar Analytics 1.7 release. 8/1/25 Doc Updates to the release notes site at https://docs.sciencelogic.com/release_notes_html/: Added Restorepoint MR20250730 release notes which addressed issues that prevented syncing in High Availability failovers; an issue that caused the Asset report to populate incorrect device data; and issues caused by missing permissions on device templates. Added Cisco: Meeting Server v102 PowerPack Release Notes which updates the PowerPack for Python 3 compatibility and addressed an issue with the "Cisco: Meeting Server CoSpaces Cache" Dynamic Application. Updated the release notes for the Skylar Analytics 1.7 release.23Views0likes2CommentsDynamic Application Guide issue
Go to Dynamic Application editor and there in Alerts page and then open Guide, search for tab_idx the example code looks like this: o_999 != 5 and tab_idx in [’.1’,’.3’,’.4’,’.6’] and explanation in the same page looks like this: Surround each index with single-quotation marks ( ‘ ) The error is not that easily visible but the single-quotation mark is ('). And even if you have done some python already before doing your copy-paste from guide to alert property window and you are like normal human and tend to believe documentation you end up having lots of system errors. The error itself is a not that self-explanatory because it blames us about using non-ascii characters in code. This issue was found on 12.1.2 and is tested to be on 12.3.4 also.Solved39Views0likes2CommentsKB article has incorrect(outdated?) command for apuser password change
Article link: https://support.sciencelogic.com/s/article/12015 While restoring a full backup our apuser passwords needed to be changed, as the password from a fresh reinstall and the password in our backup were different. I followed the above KB articles instructions, and the below command from the article to change the password only came up with errors. UPDATE user SET password=PASSWORD('new password') WHERE User='apuser'; I found article https://support.sciencelogic.com/s/article/1471 which talks about changing the MySQL User Account Passwords, and this below command seemed to work: SET password FOR 'apuser' = PASSWORD("new password"); Perhaps the KB 12015 is aimed at a different SL1 version than ours, but it would be helpful if it had different options listed. Our SL1 version is 12.1.1Solved95Views1like2CommentsScienceLogic 12.1 /gql endpoint displays incorrect contract for updateDevice(s)
When using the GraphiQL interface, you can see which GraphQL operations are available. Under 'Mutation', the operation "updateDevice" and "updateDevices" exists, which allow you to modify device properties via API. Using the normal Device Investigater Settings UI screen, we can change the SNMP Read dropdown value to whatever value we like (including 'none' to empty it), but the GQL contract does not show this option. Upon examining the action, ther browser shows that the properties "snmpReadCredentials" and "snmpReadWriteCredential" are used to update these values. I tried entering that same command in the /GQL and confirms it works; it's just showing an error in the syntax: Query: mutation UpdateDeviceSettings($deviceId: ID!, $snmpReadCredential: ID, $snmpReadWriteCredential: ID) { updateDevice(id: $deviceId, snmpReadCredential: $snmpReadCredential, snmpReadWriteCredential: $snmpReadWriteCredential) { id snmpReadCredential { id } } } Variables: { "deviceId": "10104", "snmpReadCredential": null, "snmpReadWriteCredential": null } Result: { "data": { "updateDevice": { "id": "10104", "snmpReadCredential": null } } } Error: Unknown argument: "snmpReadCredential" on diels "Mutations.updateDevice". Can this be corrected please?102Views1like2CommentsAruba Central PPK doc issue
In documentation there is a section that tells how to enable logging in that example the env_guid is wrong, no such anymore, the correct one is probably this currently: MariaDB [master]> select name, collection_env from dynamic_app where collection_env = '6E9B468D1804BAD5254508E23450F61B'; +---------------------------------------------------+----------------------------------+ | name | collection_env | +---------------------------------------------------+----------------------------------+ | Aruba: Central AP Configuration | 6E9B468D1804BAD5254508E23450F61B | | Aruba: Central AP Cache | 6E9B468D1804BAD5254508E23450F61B | | Aruba: Central AP Performance | 6E9B468D1804BAD5254508E23450F61B | | Aruba: Central Component Counts | 6E9B468D1804BAD5254508E23450F61B | | Aruba: Central SD-WAN Gateway Cache | 6E9B468D1804BAD5254508E23450F61B | | Aruba: Central SD-WAN Gateway Configuration | 6E9B468D1804BAD5254508E23450F61B | | Aruba: Central SD-WAN Gateway Performance | 6E9B468D1804BAD5254508E23450F61B | | Aruba: Central Switch Discovery | 6E9B468D1804BAD5254508E23450F61B | and even with correct env it still gives us error: The Snippet Framework log policy 'bsh-himos', [a:3372,d:119098,c:All,s:All], has been created and expires in 1 day Error occurred. 'UUID' object is not callable15Views0likes1CommentScienceLogic rest api x-em7-run-as header validation
We discovered that after updating our SL1 platform from 12.1 to 12.3 that the validation of the rest api request header "X-EM7-RUN-AS" has changed and is now more strict. In SL 12.1, we can (for example) delete an event using admin credentials and use the x-em7-run-as header to actually execute the request on behalf of a different user (in our scenario we use a customer-specific account). We used '/api/account/<accountid>' as a value for this header. Since SL 12.3 (or somewhere after 12.1), we noticed that '/api/account/<accountid>' is no longer accepted: any rest api call using the x-em7-run-as with value '/api/account/<accountid>' will return a HTTP 401 Unauthorized with corresponding message: { "errors": [ { "errorcode": "NO_AUTH", "message": "Valid authentication credentials not provided" } ], "messages": [], "resource_body": null } However, if I simply put '<accountid>' as the value for this header, the request succeeds. Can you please improve the documentation (https://docs.sciencelogic.com/api-developer-docs/Content/Web_Content_Dev_and_Integration/ScienceLogic_API/methods_headers_and_responses.htm#request-headers) and specify that the value for this header must be a number which matches a real user in the system. Also, the request also fails when using an account id value and that account is Inactive. Would be nice to read it in the docs. error message when trying to execute an action on a suspended user: { "errors": [ { "errorcode": "NO_AUTH", "message": "Account \u0027em7admin\u0027 failed authentication due to 1 account restriction(s)" } ], "messages": [ "This account is marked as \u0022inactive\u0022" ], "resource_body": null }Solved49Views1like1CommentPhonehome documentation issue
Hi, In latest documentations the phonehome command to add port forwards miswritten. The command in documentation is "phonehome forward add :10022 :22" but at least in 12.1.1 and .2 the command is 'phonehome forwards add :10022 :22'. So the s is missing from docsSolved41Views0likes1CommentIncorrect procedure for upgrading MariaDB on Collectors since SL12
Hello, It seems the procedure for manual upgrading the MariaDB on collectors has changed since SL 12. The procedure however has not been updated. Location: https://docs.sciencelogic.com/latest/Content/Web_Admin_and_Accounts/System_Administration/sys_admin_system_upgrade.htm#manually-upgrading-standalone-database-servers-all-in-one-applia In fact, the manual mariadb upgrade on SL 12 is no longer supported and executing the procedure will make the collector unusuable.51Views1like1CommentRequest documentation update on SNMP Traps
The latest ScienceLogic documentation still has sections to execute when you are still using SL1 8 or 10. They can be removed from the documentation as it causes confusion Link to the docs: https://docs.sciencelogic.com/latest/Content/Web_Events_and_Automation/Syslogs_and_Traps/snmp_traps.htm#manually-configuring-snmpv3-traps71Views0likes1CommentHow many docs sites ARE there at docs.sciencelogic.com?
If you go to https://docs.sciencelogic.com/, you might think that there is only one documentation site at that address. However, the ScienceLogic Documentation team maintains multiple "sites" at that location. Here's a quick primer on each site, and what you can find there. The docs sites maintained by the Documentation team include the following: https://docs.sciencelogic.com/latest/ - the "main" docs site, which contains all of the various in-depth manuals for the different features for SL1, SL1 PowerPacks, SL1 PowerFlow, and PowerFlow SyncPacks, along with additional supporting docs. https://docs.sciencelogic.com/release_notes_html/ - the release notes site, which contains brief, release-specific documents for all ScienceLogic products. https://docs.sciencelogic.com/restorepoint/latest/ - the Restorepoint site, which covers how to configure and use Restorepoint, a disaster recovery and secure configuration management appliance for network devices. https://docs.sciencelogic.com/zebrium/latest/ - the Skylar Automated RCA (formerly Zebrium) site, which covers how to configure and use Skylar AI in conjunction with SL1 to automatically find the root cause of software issues. NOTE: Since this post went live, this site was updated to contain all of the Skylar products so far, include Skylar Automate RCA and Skylar Analytics, with more Skylar products coming soon. The Skylar products are also part of the main docs site as well: Skylar AI. The content is the same in both locations. The following sites are hosted at the docs site, but are not maintained by the Documentation team: https://docs.sciencelogic.com/dev-docs/ - the SL1 developer documentation site, which includes docs for Low-code Tools, Snippet Framework, CLI Toolkit, Prometheus Toolkit, REST Toolkit, Snippet API, and the PowerPack Quality Assessment Tool. Please note the the Documentation team only hosts these docs, but we do not actually write these docs (the developers do that). https://docs.sciencelogic.com/restorepoint/api/5-6/api.html - the Restorepoint RESTful API site, which is also hosted by the Documentation team but updated by the developers. Typically the Documentation team updates the docs sites at least once a week, if not more often. Watch this space for more information about our documentation updates every week.101Views3likes1Comment
About Product Documentation
Learn about documentation updates, ask questions, and share feedback about the docs.
Owned by: joshneighbors, Mike_Jasper, Bryan_Anderton, and SaraLeslieAdminCreated: 2 years agoOpen Group