Commit graph

4 commits

Author SHA1 Message Date
Rachael Shaw
5f442a8002
Tiny tweak to a comment (#18709)
Just making it a touch clearer why we're changing a key name/deleting a
key from the Open API response.
2024-05-02 17:39:39 -05:00
Rachael Shaw
81a98ec54b
Update prompt for API endpoint to get human interpretation of osquery SQL (#18695)
When using this API many times in a row to try and populate real policy
descriptions/resolutions, I discovered a problem: the inferred
resolution (“What we’ll do”) almost never used decisive language, so
you'd get a lot of “probably”, etc., when we really want it to sound
more confident about what will happen during the maintenance window.
(The calendar events say what WILL happen to your device, not what
should probably happen.)

After several attempts to tweak the prompt, I ended up getting the best
results by just removing "probably" from
`whatWillProbablyHappenDuringMaintenance`. I made this change to the
prompt without changing the data that this API returns.

---------

Co-authored-by: Eric <[email protected]>
2024-05-01 19:18:12 -05:00
Rachael Shaw
850e429b80
Better error handling in "Get human interpretation from osquery sql" (#18529)
+ Use the same "Failed to generate human interpretation using generative
AI." message if you send it something weird like "asdf" (so you don't
get a vague 500 error).
+ Simplify the code a bit

---------

Co-authored-by: Eric <[email protected]>
2024-04-25 10:19:16 -05:00
Rachael Shaw
3e37b1b625
Stub out basis for AI-generated employee experience tips and risk register (#18501)
Add new fleetdm.com API endpoint for #18187

---------

Co-authored-by: Mike McNeil <[email protected]>
2024-04-24 14:54:50 -05:00