This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Creating a user with API rights only to Orion.Events table


I have some API calls that read and write to Orion.Events table, but for now am using an account with admin rights.

Is there a way to create a user the least privileges, I just need to have read and write rights to only Orion.Events table?


Parents Reply Children
  • Thank you !

    I did upvote the feature request.

    I'm still checking on my side also, please let me know if you find any option.

  • I tried all kinds of different permissions, and I couldn't find a way without granting admin rights to create event entries.

    What's your exact use case?  There's a chance the alerting engine could do it for you.

  • My use case is:

    1. Inserting new records on Orion.Events table using POST request to:
    2. Reading from Orion.Events table using GET request from:
      ORION-IP:17778/.../Query EventTime,Message FROM Orion.Events where EventType = XXXX or EventType = XXXX ORDER BY EventTime ASC;"
    3. Reading from Orion.AlertHistory table using GET request from:
      ORION-IP:17778/.../Query TOP 10 TimeStamp, Message FROM Orion.AlertHistory where (AlertObjectID = XXXX or AlertObjectID = XXXX )  order by TimeStamp desc
  • Yerah - sorry.  Maybe I was unclear.  What would cause #1 from above?

  • I have some custom HTMLs with JS scripts interacting with other systems.

    For logging purposes, I'm inserting records into Orion.Events table, which will be used later to generate a report using the query in #2.

  • That's what I was looking for.  Is it a web page or something that can be "read" by the SolarWinds Platform?  If so, they might be able to use the alerting engine to trigger the event.


    1. If the web page contains the word "down."
    2. Trigger an alert.
    3. Alert Action: Write something to the Event Log.

    Otherwise, I'm afraid you'd going to either need to use an admin account or directly edit the SQL table (which is a very bad idea).