curl --request GET \
--url https://developer.synq.io/api/triage/v1/conclusions \
--header 'Authorization: Bearer <token>'{
"conclusions": [
{
"conclusion": {
"issueIds": [
"3c90c3cc-0d44-4b50-8888-8dd25736052a"
],
"title": "<string>",
"addToIncident": {
"incidentId": "<string>"
},
"conclusionId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"summary": "<string>",
"concludedAt": "2023-11-07T05:31:56Z",
"isFinalConclusion": true
},
"originalIssueIds": [
"<string>"
],
"evidence": [
{
"issueIds": [
"3c90c3cc-0d44-4b50-8888-8dd25736052a"
],
"title": "<string>",
"analysis": {
"analysis": "<string>",
"sqlQueries": [
"<string>"
]
},
"evidenceId": "3c90c3cc-0d44-4b50-8888-8dd25736052a"
}
],
"userFeedback": {
"accept": {},
"user": "<string>",
"feedbackAt": "2023-11-07T05:31:56Z"
}
}
]
}Retrieves the latest triage state for one or more issues. This method is used by the LLM agent to retrieve the current state of the issues it is working on.
curl --request GET \
--url https://developer.synq.io/api/triage/v1/conclusions \
--header 'Authorization: Bearer <token>'{
"conclusions": [
{
"conclusion": {
"issueIds": [
"3c90c3cc-0d44-4b50-8888-8dd25736052a"
],
"title": "<string>",
"addToIncident": {
"incidentId": "<string>"
},
"conclusionId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
"summary": "<string>",
"concludedAt": "2023-11-07T05:31:56Z",
"isFinalConclusion": true
},
"originalIssueIds": [
"<string>"
],
"evidence": [
{
"issueIds": [
"3c90c3cc-0d44-4b50-8888-8dd25736052a"
],
"title": "<string>",
"analysis": {
"analysis": "<string>",
"sqlQueries": [
"<string>"
]
},
"evidenceId": "3c90c3cc-0d44-4b50-8888-8dd25736052a"
}
],
"userFeedback": {
"accept": {},
"user": "<string>",
"feedbackAt": "2023-11-07T05:31:56Z"
}
}
]
}Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
List of issue IDs for which latest conclusion should be returned.
Success
Show child attributes
IssueConclusion represents the final determination made by the LLM agent about an issue.
Show child attributes
List of issue IDs that should be concluded with the specified conclusion.
Brief, single-line description summarizing the triage conclusion. Max 5 words.
Unique identifier of the conclusion.
Detailed markdown-formatted description explaining the conclusion and the reasoning based on all collected evidence.
Timestamp when the conclusion was made.
Indicates that this is final conclusion and SRE agent won't change it unless new evidence is provided to change it.
List of issues for which original conclusion was created.
Collection of structured evidence items collected during the investigation.
EvidenceItem represents a single piece of evidence collected during the triage investigation. Each evidence item must have a title and one of the specific evidence types.
Show child attributes
List of issue IDs that should be annotated with the provided evidence. Each ID must be a valid UUID.
Brief, descriptive title summarizing the type of evidence collected. This helps in quickly understanding the nature of the evidence.
Evidence containing detailed analysis of the issue. DEPRECATED: This type will be gradually retired in favor of more specific evidence types like DataQueryEvidenceV2 and OtherEvidence. Please use those types for new evidence.
Show child attributes
Detailed analysis of the issue, including observations, patterns, and potential implications. This should provide clear reasoning for the conclusions drawn.
SQL queries which were executed to investigate the issue and collect the evidence.
Unique identifier of the evidence item.
Optional feedback given by the user on the SRE generated conclusion.
Show child attributes
A Timestamp represents a point in time independent of any time zone or local calendar, encoded as a count of seconds and fractions of seconds at nanosecond resolution. The count is relative to an epoch at UTC midnight on January 1, 1970, in the proleptic Gregorian calendar which extends the Gregorian calendar backwards to year one.
All minutes are 60 seconds long. Leap seconds are "smeared" so that no leap second table is needed for interpretation, using a 24-hour linear smear.
The range is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z. By restricting to that range, we ensure that we can convert to and from RFC 3339 date strings.
Example 1: Compute Timestamp from POSIX time().
Timestamp timestamp;
timestamp.set_seconds(time(NULL));
timestamp.set_nanos(0);Example 2: Compute Timestamp from POSIX gettimeofday().
struct timeval tv;
gettimeofday(&tv, NULL);
Timestamp timestamp;
timestamp.set_seconds(tv.tv_sec);
timestamp.set_nanos(tv.tv_usec * 1000);Example 3: Compute Timestamp from Win32 GetSystemTimeAsFileTime().
FILETIME ft;
GetSystemTimeAsFileTime(&ft);
UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime;
// A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z
// is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z.
Timestamp timestamp;
timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL));
timestamp.set_nanos((INT32) ((ticks % 10000000) * 100));Example 4: Compute Timestamp from Java System.currentTimeMillis().
long millis = System.currentTimeMillis();
Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000)
.setNanos((int) ((millis % 1000) * 1000000)).build();Example 5: Compute Timestamp from Java Instant.now().
Instant now = Instant.now();
Timestamp timestamp =
Timestamp.newBuilder().setSeconds(now.getEpochSecond())
.setNanos(now.getNano()).build();Example 6: Compute Timestamp from current time in Python.
timestamp = Timestamp()
timestamp.GetCurrentTime()In JSON format, the Timestamp type is encoded as a string in the RFC 3339 format. That is, the format is "{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z" where {year} is always expressed using four digits while {month}, {day}, {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution), are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone is required. A proto3 JSON serializer should always use UTC (as indicated by "Z") when printing the Timestamp type and a proto3 JSON parser should be able to accept both UTC and other timezones (as indicated by an offset).
For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past 01:30 UTC on January 15, 2017.
In JavaScript, one can convert a Date object to this format using the
standard
toISOString()
method. In Python, a standard datetime.datetime object can be converted
to this format using
strftime with
the time format spec '%Y-%m-%dT%H:%M:%S.%fZ'. Likewise, in Java, one can use
the Joda Time's ISODateTimeFormat.dateTime() to obtain a formatter capable of generating timestamps in this format.